Group bearer and bearer selection for multicast/broadcast data transmissions

ABSTRACT

A method, an apparatus, and a computer program product for wireless communication are provided. The apparatus may be a UE that receives a multicast/broadcast data transmission via a group bearer. The UE receives a paging message including a type of the group bearer. In addition, the UE determines whether to remain in or change to an RRC idle mode or an RRC connected mode based on the type of the group bearer received in the paging message.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of PCT Application No. PCT/CN2013/074360, entitled “MBMS BEARER ENHANCEMENTS FOR PUSH TO TALK OR PUSH TO EVERYTHING VIA EMBMS” and filed on Apr. 18, 2013, which is expressly incorporated by reference herein in its entirety.

BACKGROUND

1. Field

The present disclosure relates generally to communication systems, and more particularly, to group bearer and bearer selection for multicast/broadcast data transmissions.

2. Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example of an emerging telecommunication standard is Long Term Evolution (LTE). LTE is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA on the downlink (DL), SC-FDMA on the uplink (UL), and multiple-input multiple-output (MIMO) antenna technology. However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE technology. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

In an aspect of the disclosure, a method, a computer program product, and an apparatus are provided. The apparatus may be a user equipment (UE) that receives a multicast/broadcast data transmission via a group bearer. The UE receives a paging message including a type of the group bearer. In addition, the UE determines whether to remain in or change to a radio resource control (RRC) idle mode or an RRC connected mode based on the type of the group bearer received in the paging message.

In an aspect of the disclosure, a method, a computer program product, and an apparatus are provided. The apparatus may be an evolved Node B (eNB) that provides a multicast/broadcast data transmission via a group bearer. The eNB determines a type of the group bearer. In addition, the eNB sends a paging message including the type of the group bearer to a set of UEs.

In an aspect of the disclosure, a method, a computer program product, and an apparatus are provided. The apparatus determines a type of a bearer and establishes the bearer for PTT/PTX communication. The apparatus receives a PTT/PTX message for a set of UEs. The apparatus establishes one of a unicast bearer, a group bearer, or a Multimedia Broadcast Multicast Service (MBMS) bearer based on at least one of the PTT/PTX message or the set of UEs. The apparatus sends the PTT/PTX message through the established bearer to the set of UEs.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a network architecture.

FIG. 2 is a diagram illustrating an example of an access network.

FIG. 3 is a diagram illustrating an example of a DL frame structure in LTE.

FIG. 4 is a diagram illustrating an example of an UL frame structure in LTE.

FIG. 5 is a diagram illustrating an example of a radio protocol architecture for the user and control planes.

FIG. 6 is a diagram illustrating an example of an evolved Node B and user equipment in an access network.

FIG. 7A is a diagram illustrating an example of an enhanced Multimedia Broadcast Multicast Service (MBMS) (eMBMS) channel configuration in a Multicast Broadcast Single Frequency Network (SFN) (MBSFN).

FIG. 7B is a diagram illustrating a format of a Multicast Channel Scheduling Information Media Access Control control element.

FIG. 7C is a diagram illustrating MBMS over MBSFN areas within an MBMS service area.

FIG. 8 is a diagram for illustrating an exemplary method for adaptively configuring multicast broadcast service areas/MBSFN areas.

FIG. 9 is a diagram illustrating a first exemplary architecture for adaptively configuring multicast broadcast service areas/MBSFN areas.

FIG. 10 is a diagram illustrating a first exemplary signaling design for an adaptive MBSFN.

FIG. 11 is a diagram illustrating a second exemplary signaling design for an adaptive MBSFN.

FIG. 12 is a diagram illustrating a second exemplary architecture for adaptively configuring multicast broadcast service areas/MBSFN areas.

FIG. 13 is a diagram illustrating a third exemplary signaling design for an adaptive MBSFN.

FIG. 14 is a diagram illustrating PTT/PTX through eMBMS.

FIG. 15 is a diagram illustrating a first call flow using an MBMS bearer.

FIG. 16 is a diagram illustrating a second call flow using an MBMS bearer.

FIG. 17 is a diagram illustrating a first parallel call setup.

FIG. 18 is a diagram illustrating a second parallel call setup.

FIG. 19 is a diagram for illustrating security enhancements with an MBMS bearer for PTT/PTX.

FIG. 20 is a flow chart of a first method of wireless communication.

FIG. 21 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in a first exemplary apparatus.

FIG. 22 is a diagram illustrating an example of a hardware implementation for the first exemplary apparatus employing a processing system.

FIG. 23 is a flow chart of a second method of wireless communication.

FIG. 24 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in a second exemplary apparatus.

FIG. 25 is a diagram illustrating an example of a hardware implementation for the second exemplary apparatus employing a processing system.

FIG. 26 is a flow chart of a third method of wireless communication.

FIG. 27 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in a third exemplary apparatus.

FIG. 28 is a diagram illustrating an example of a hardware implementation for the third exemplary apparatus employing a processing system.

FIG. 29 is a flow chart of a fourth method of wireless communication.

FIG. 30 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in a fourth exemplary apparatus.

FIG. 31 is a diagram illustrating an example of a hardware implementation for the fourth exemplary apparatus employing a processing system.

FIG. 32 is a diagram illustrating PTT/PTX through unicast, group, and MBMS bearers.

FIG. 33 is a diagram illustrating a group bearer establishment procedure.

FIG. 34 is a flow chart of a method of a UE of receiving a multicast/broadcast data transmission via a group bearer.

FIG. 35 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in a fifth exemplary apparatus.

FIG. 36 is a diagram illustrating an example of a hardware implementation for the fifth exemplary apparatus employing a processing system.

FIG. 37 is a flow chart of a method of an eNB of providing a multicast/broadcast data transmission via a group bearer.

FIG. 38 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in a sixth exemplary apparatus.

FIG. 39 is a diagram illustrating an example of a hardware implementation for the sixth exemplary apparatus employing a processing system.

FIG. 40 is a flow chart of a method of PTT/PTX communication.

FIG. 41 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in a seventh exemplary apparatus.

FIG. 42 is a diagram illustrating an example of a hardware implementation for the seventh exemplary apparatus employing a processing system.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented with a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and floppy disk where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

FIG. 1 is a diagram illustrating an LTE network architecture 100. The LTE network architecture 100 may be referred to as an Evolved Packet System (EPS) 100. The EPS 100 may include one or more user equipment (UE) 102, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 104, an Evolved Packet Core (EPC) 110, a Home Subscriber Server (HSS) 120, and an Operator's Internet Protocol (IP) Services 122. The EPS can interconnect with other access networks, but for simplicity those entities/interfaces are not shown. As shown, the EPS provides packet-switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure may be extended to networks providing circuit-switched services.

The E-UTRAN includes the evolved Node B (eNB) 106 and other eNBs 108. The eNB 106 provides user and control planes protocol terminations toward the UE 102. The eNB 106 may be connected to the other eNBs 108 via a backhaul (e.g., an X2 interface). The eNB 106 may also be referred to as a base station, a Node B, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), or some other suitable terminology. The eNB 106 provides an access point to the EPC 110 for a UE 102. Examples of UEs 102 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, or any other similar functioning device. The UE 102 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

The eNB 106 is connected to the EPC 110. The EPC 110 may include a Mobility Management Entity (MME) 112, other MMEs 114, a Serving Gateway 116, a Multimedia Broadcast Multicast Service (MBMS) Gateway 124, a Broadcast Multicast Service Center (BM-SC) 126, and a Packet Data Network (PDN) Gateway 118. The MME 112 is the control node that processes the signaling between the UE 102 and the EPC 110. Generally, the MME 112 provides bearer and connection management. All user IP packets are transferred through the Serving Gateway 116, which itself is connected to the PDN Gateway 118. The PDN Gateway 118 provides UE IP address allocation as well as other functions. The PDN Gateway 118 is connected to the Operator's IP Services 122. The Operator's IP Services 122 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), and a PS Streaming Service (PSS). The BM-SC 126 may provide functions for MBMS user service provisioning and delivery. The BM-SC 126 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a PLMN, and may be used to schedule and deliver MBMS transmissions. The MBMS Gateway 124 may be used to distribute MBMS traffic to the eNBs (e.g., 106, 108) belonging to an MBSFN area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

FIG. 2 is a diagram illustrating an example of an access network 200 in an LTE network architecture. In this example, the access network 200 is divided into a number of cellular regions (cells) 202. One or more lower power class eNBs 208 may have cellular regions 210 that overlap with one or more of the cells 202. The lower power class eNB 208 may be a femto cell (e.g., home eNB (HeNB)), pico cell, micro cell, or remote radio head (RRH). The macro eNBs 204 are each assigned to a respective cell 202 and are configured to provide an access point to the EPC 110 for all the UEs 206 in the cells 202. There is no centralized controller in this example of an access network 200, but a centralized controller may be used in alternative configurations. The eNBs 204 are responsible for all radio related functions including radio bearer control, admission control, mobility control, scheduling, security, and connectivity to the serving gateway 116. An eNB may support one or multiple (e.g., three) cells (also referred to as a sector). The term “cell” can refer to the smallest coverage area of an eNB and/or an eNB subsystem serving are particular coverage area. Further, the terms “eNB,” “base station,” and “cell” may be used interchangeably herein.

The modulation and multiple access scheme employed by the access network 200 may vary depending on the particular telecommunications standard being deployed. In LTE applications, OFDM is used on the DL and SC-FDMA is used on the UL to support both frequency division duplex (FDD) and time division duplex (TDD). As those skilled in the art will readily appreciate from the detailed description to follow, the various concepts presented herein are well suited for LTE applications. However, these concepts may be readily extended to other telecommunication standards employing other modulation and multiple access techniques. By way of example, these concepts may be extended to Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. These concepts may also be extended to Universal Terrestrial Radio Access (UTRA) employing Wideband-CDMA (W-CDMA) and other variants of CDMA, such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDMA. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from the 3GPP organization. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.

The eNBs 204 may have multiple antennas supporting MIMO technology. The use of MIMO technology enables the eNBs 204 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing may be used to transmit different streams of data simultaneously on the same frequency. The data streams may be transmitted to a single UE 206 to increase the data rate or to multiple UEs 206 to increase the overall system capacity. This is achieved by spatially precoding each data stream (i.e., applying a scaling of an amplitude and a phase) and then transmitting each spatially precoded stream through multiple transmit antennas on the DL. The spatially precoded data streams arrive at the UE(s) 206 with different spatial signatures, which enables each of the UE(s) 206 to recover the one or more data streams destined for that UE 206. On the UL, each UE 206 transmits a spatially precoded data stream, which enables the eNB 204 to identify the source of each spatially precoded data stream.

Spatial multiplexing is generally used when channel conditions are good. When channel conditions are less favorable, beamforming may be used to focus the transmission energy in one or more directions. This may be achieved by spatially precoding the data for transmission through multiple antennas. To achieve good coverage at the edges of the cell, a single stream beamforming transmission may be used in combination with transmit diversity.

In the detailed description that follows, various aspects of an access network will be described with reference to a MIMO system supporting OFDM on the DL. OFDM is a spread-spectrum technique that modulates data over a number of subcarriers within an OFDM symbol. The subcarriers are spaced apart at precise frequencies. The spacing provides “orthogonality” that enables a receiver to recover the data from the subcarriers. In the time domain, a guard interval (e.g., cyclic prefix) may be added to each OFDM symbol to combat inter-OFDM-symbol interference. The UL may use SC-FDMA in the form of a DFT-spread OFDM signal to compensate for high peak-to-average power ratio (PAPR).

FIG. 3 is a diagram 300 illustrating an example of a DL frame structure in LTE. A frame (10 ms) may be divided into 10 equally sized subframes. Each subframe may include two consecutive time slots. A resource grid may be used to represent two time slots, each time slot including a resource block. The resource grid is divided into multiple resource elements. In LTE, a resource block contains 12 consecutive subcarriers in the frequency domain and, for a normal cyclic prefix in each OFDM symbol, 7 consecutive OFDM symbols in the time domain, or 84 resource elements. For an extended cyclic prefix, a resource block contains 6 consecutive OFDM symbols in the time domain and has 72 resource elements. Some of the resource elements, indicated as R 302, 304, include DL reference signals (DL-RS). The DL-RS include Cell-specific RS (CRS) (also sometimes called common RS) 302 and UE-specific RS (UE-RS) 304. UE-RS 304 are transmitted only on the resource blocks upon which the corresponding physical DL shared channel (PDSCH) is mapped. The number of bits carried by each resource element depends on the modulation scheme. Thus, the more resource blocks that a UE receives and the higher the modulation scheme, the higher the data rate for the UE.

FIG. 4 is a diagram 400 illustrating an example of an UL frame structure in LTE. The available resource blocks for the UL may be partitioned into a data section and a control section. The control section may be formed at the two edges of the system bandwidth and may have a configurable size. The resource blocks in the control section may be assigned to UEs for transmission of control information. The data section may include all resource blocks not included in the control section. The UL frame structure results in the data section including contiguous subcarriers, which may allow a single UE to be assigned all of the contiguous subcarriers in the data section.

A UE may be assigned resource blocks 410 a, 410 b in the control section to transmit control information to an eNB. The UE may also be assigned resource blocks 420 a, 420 b in the data section to transmit data to the eNB. The UE may transmit control information in a physical UL control channel (PUCCH) on the assigned resource blocks in the control section. The UE may transmit only data or both data and control information in a physical UL shared channel (PUSCH) on the assigned resource blocks in the data section. A UL transmission may span both slots of a subframe and may hop across frequency.

A set of resource blocks may be used to perform initial system access and achieve UL synchronization in a physical random access channel (PRACH) 430. The PRACH 430 carries a random sequence and cannot carry any UL data/signaling. Each random access preamble occupies a bandwidth corresponding to six consecutive resource blocks. The starting frequency is specified by the network. That is, the transmission of the random access preamble is restricted to certain time and frequency resources. There is no frequency hopping for the PRACH. The PRACH attempt is carried in a single subframe (1 ms) or in a sequence of few contiguous subframes and a UE can make only a single PRACH attempt per frame (10 ms).

FIG. 5 is a diagram 500 illustrating an example of a radio protocol architecture for the user and control planes in LTE. The radio protocol architecture for the UE and the eNB is shown with three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various physical layer signal processing functions. The L1 layer will be referred to herein as the physical layer 506. Layer 2 (L2 layer) 508 is above the physical layer 506 and is responsible for the link between the UE and eNB over the physical layer 506.

In the user plane, the L2 layer 508 includes a media access control (MAC) sublayer 510, a radio link control (RLC) sublayer 512, and a packet data convergence protocol (PDCP) 514 sublayer, which are terminated at the eNB on the network side. Although not shown, the UE may have several upper layers above the L2 layer 508 including a network layer (e.g., IP layer) that is terminated at the PDN gateway 118 on the network side, and an application layer that is terminated at the other end of the connection (e.g., far end UE, server, etc.).

The PDCP sublayer 514 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 514 also provides header compression for upper layer data packets to reduce radio transmission overhead, security by ciphering the data packets, and handover support for UEs between eNBs. The RLC sublayer 512 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to hybrid automatic repeat request (ARQ) (HARQ). The MAC sublayer 510 provides multiplexing between logical and transport channels. The MAC sublayer 510 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 510 is also responsible for HARQ operations.

In the control plane, the radio protocol architecture for the UE and eNB is substantially the same for the physical layer 506 and the L2 layer 508 with the exception that there is no header compression function for the control plane. The control plane also includes a radio resource control (RRC) sublayer 516 in Layer 3 (L3 layer). The RRC sublayer 516 is responsible for obtaining radio resources (e.g., radio bearers) and for configuring the lower layers using RRC signaling between the eNB and the UE.

FIG. 6 is a block diagram of an eNB 610 in communication with a UE 650 in an access network. In the DL, upper layer packets from the core network are provided to a controller/processor 675. The controller/processor 675 implements the functionality of the L2 layer. In the DL, the controller/processor 675 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to the UE 650 based on various priority metrics. The controller/processor 675 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the UE 650.

The transmit (TX) processor 616 implements various signal processing functions for the L1 layer (i.e., physical layer). The signal processing functions include coding and interleaving to facilitate forward error correction (FEC) at the UE 650 and mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then split into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 674 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 650. Each spatial stream may then be provided to a different antenna 620 via a separate transmitter 618TX. Each transmitter 618TX may modulate an RF carrier with a respective spatial stream for transmission, if applicable.

At the UE 650, each receiver 654RX receives a signal through its respective antenna 652. Each receiver 654RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 656. The RX processor 656 implements various signal processing functions of the L1 layer. The RX processor 656 may perform spatial processing on the information to recover any spatial streams destined for the UE 650. If multiple spatial streams are destined for the UE 650, they may be combined by the RX processor 656 into a single OFDM symbol stream. The RX processor 656 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each sub carrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 610. These soft decisions may be based on channel estimates computed by the channel estimator 658. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 610 on the physical channel. The data and control signals are then provided to the controller/processor 659.

The controller/processor 659 implements the L2 layer. The controller/processor can be associated with a memory 660 that stores program codes and data. The memory 660 may be referred to as a computer-readable medium. In the UL, the controller/processor 659 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packets are then provided to a data sink 662, which represents all the protocol layers above the L2 layer. Various control signals may also be provided to the data sink 662 for L3 processing. The controller/processor 659 is also responsible for error detection using an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support HARQ operations.

In the UL, a data source 667 is used to provide upper layer packets to the controller/processor 659. The data source 667 represents all protocol layers above the L2 layer. Similar to the functionality described in connection with the DL transmission by the eNB 610, the controller/processor 659 implements the L2 layer for the user plane and the control plane by providing header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations by the eNB 610. The controller/processor 659 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the eNB 610.

Channel estimates derived by a channel estimator 658 from a reference signal or feedback transmitted by the eNB 610 may be used by the TX processor 668 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 668 may be provided to different antenna 652 via separate transmitters 654TX. Each transmitter 654TX may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the eNB 610 in a manner similar to that described in connection with the receiver function at the UE 650. Each receiver 618RX receives a signal through its respective antenna 620. Each receiver 618RX recovers information modulated onto an RF carrier and provides the information to a RX processor 670. The RX processor 670 may implement the L1 layer.

The controller/processor 675 implements the L2 layer. The controller/processor 675 can be associated with a memory 676 that stores program codes and data. The memory 676 may be referred to as a computer-readable medium. In the UL, the control/processor 675 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 650. Upper layer packets from the controller/processor 675 may be provided to the core network. The controller/processor 675 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

FIG. 7A is a diagram 750 illustrating an example of an eMBMS channel configuration in an MBSFN. The eNBs 752 in cells 752′ may form a first MBSFN area and the eNBs 754 in cells 754′ may form a second MBSFN area. The eNBs 752, 754 may each be associated with other MBSFN areas, for example, up to a total of eight MBSFN areas. A cell within an MBSFN area may be designated a reserved cell. Reserved cells do not provide multicast/broadcast content, but are time-synchronized to the cells 752′, 754′ and have restricted power on MBSFN resources in order to limit interference to the MBSFN areas. Each eNB in an MBSFN area synchronously transmits the same eMBMS control information and data. Each area may support broadcast, multicast, and unicast services. A unicast service is a service intended for a specific user, e.g., a voice call. A multicast service is a service that may be received by a group of users, e.g., a subscription video service. A broadcast service is a service that may be received by all users, e.g., a news broadcast. Referring to FIG. 7A, the first MBSFN area may support a first eMBMS broadcast service, such as by providing a particular news broadcast to UE 770. The second MBSFN area may support a second eMBMS broadcast service, such as by providing a different news broadcast to UE 760. Each MBSFN area supports a plurality of physical multicast channels (PMCH) (e.g., 15 PMCHs). Each PMCH corresponds to a multicast channel (MCH). Each MCH can multiplex a plurality (e.g., 29) of multicast logical channels. Each MBSFN area may have one multicast control channel (MCCH). As such, one MCH may multiplex one MCCH and a plurality of multicast traffic channels (MTCHs) and the remaining MCHs may multiplex a plurality of MTCHs.

A UE can camp on an LTE cell to discover the availability of eMBMS service access and a corresponding access stratum configuration. In a first step, the UE may acquire a system information block (SIB) 13 (SIB13). In a second step, based on the SIB13, the UE may acquire an MBSFN Area Configuration message on an MCCH. In a third step, based on the MBSFN Area Configuration message, the UE may acquire an MCH scheduling information (MSI) MAC control element. The SIB13 indicates (1) an MBSFN area identifier of each MBSFN area supported by the cell; (2) information for acquiring the MCCH such as an MCCH repetition period (e.g., 32, 64, . . . , 256 frames), an MCCH offset (e.g., 0, 1, . . . , 10 frames), an MCCH modification period (e.g., 512, 1024 frames), a signaling modulation and coding scheme (MCS), subframe allocation information indicating which subframes of the radio frame as indicated by repetition period and offset can transmit MCCH; and (3) an MCCH change notification configuration. There is one MBSFN Area Configuration message for each MBSFN area. The MBSFN Area Configuration message indicates both (1) a temporary mobile group identity (TMGI) and an optional session identifier of each MTCH identified by a logical channel identifier within the PMCH, (2) allocated resources (i.e., radio frames and subframes) for transmitting each PMCH of the MBSFN area and the allocation period (e.g., 4, 8, . . . , 256 frames) of the allocated resources for all the PMCHs in the area, and (3) an MCH scheduling period (MSP) (e.g., 8, 16, 32, . . . , or 1024 radio frames) over which the MSI MAC control element is transmitted.

FIG. 7B is a diagram 790 illustrating the format of an MSI MAC control element. The MSI MAC control element may be sent once each MSP. The MSI MAC control element may be sent in the first subframe of each scheduling period of the PMCH. The MSI MAC control element can indicate the stop frame and subframe of each MTCH within the PMCH. There may be one MSI per PMCH per MBSFN area.

FIG. 7C is a diagram 780 illustrating MBMS over MBSFN areas within an MBMS service area. FIG. 7C illustrates a system including an MBMS service area 732 encompassing multiple MBSFN areas 734, 736, 738, which themselves include multiple cells or base stations 740. As used herein, an “MBMS service area” refers to a group of wireless transmission cells where a certain MBMS service is available. For example, a particular sports or other program may be broadcast by base stations within the MBMS service area at a particular time. The area where the particular program is broadcast defines the MBMS service area. The MBMS service area may be made up of one or more “MBSFN areas” as shown at 734, 736 and 738. As used herein, an MBSFN area refers to a group of cells (e.g., cells 740) currently broadcasting a particular program in a synchronized manner using an MBSFN protocol. An “MBSFN synchronization area” refers to a group of cells that are interconnected and configured in a way such that they are capable of operating in a synchronized fashion to broadcast a particular program using an MBSFN protocol, regardless of whether or not they are currently doing so. Each eNB can belong to only one MBSFN synchronization area, on a given frequency layer. It is worth noting that an MBMS service area 732 may include one or more MBSFN synchronization areas (not shown). Conversely, an MBSFN synchronization area may include one or more MBSFN areas or MBMS service areas. Generally, an MBSFN area is made up of all, or a portion of, a single MBSFN synchronization area and is located within a single MBMS service area. Overlap between various MBSFN areas is supported, and a single eNB may belong to several different MBSFN areas. For example, up to 8 independent MCCHs may be configured in System Information Block (SIB) 13 to support membership in different MBSFN areas. An MBSFN Area Reserved Cell or Base Station is a cell/base station within a MBSFN Area that does not contribute to the MBSFN transmission, for example a cell near a MBSFN Synchronization Area boundary, or a cell that that is not needed for MBSFN transmission because of its location.

With an increase in eMBMS popularity, adaptively configuring multicast broadcast service areas (e.g., MBSFN service areas, MBMS service areas) or MBSFN areas based on available resources and user distribution could be beneficial. Through the adaptive configuration of multicast broadcast service areas/MBSFN areas, cells may be added or removed according to actual needs. By allowing the adaptive configuration of multicast broadcast service areas/MBSFN areas, system resource utilization may be increased, easy of operations/configurations may be improved, interference may be reduced through the use of tiers, and eMBMS may be provided on demand when a sufficient number of users desire the same service.

FIG. 8 is a diagram 800 for illustrating an exemplary method for adaptively configuring multicast broadcast service areas/MBSFN areas. As shown in FIG. 8, a multicast broadcast service area 812 may include cells 802-810 corresponding to the eNBs 802 a, 802 b, 802 c, 802 d, 804 a, 804 b, 804 c, 806 a, 808 a, and 810 a. One or more of the eNBs within the multicast broadcast service area 812 may determine UE count information indicating a number of UEs served by the eNBs. Each of the one or more of the eNBs then sends the UE count information to a network entity, such as a Multicast Coordination Entity (MCE) or a BM-SC. Each of the one or more of the eNBs may also receive signal quality information from each of the UEs served by the corresponding eNB. The signal quality information is with respect to the serving base station and neighboring base stations. For example, the eNB 802 b may receive signal quality information from each of the UEs 820, 822, 824. The signal quality information may be with respect to unicast transmissions and/or multicast/broadcast transmissions and may include at least one of reference signal received power (RSRP) information, reference signal received quality (RSRQ) information, a receive strength signal indicator (RSSI), or a signal to interference plus noise ratio (SINR). Accordingly, the eNB 802 b may receive signal quality information from the UE 820 based on unicast and/or multicast/broadcast transmissions from the eNBs 802 b, 804 b, 804 c; from the UE 822 based on unicast and/or multicast/broadcast transmissions from the eNBs 802 b, 804 c, 806 a; and from the UE 824 based on unicast and/or multicast/broadcast transmissions from the eNBs 802 b, 802 c, 802 d. Each of the one or more of the eNBs then sends the signal quality information to the network entity, such as the MCE or the BM-SC.

Based on the UE count information, the MCE or BM-SC determines whether a base station should be part of the multicast broadcast service area 812 and/or an MBSFN area within the multicast broadcast service area 812. The MCE or BM-SC may make the determination further based on the received signal quality information. For example, upon receiving the UE count information and signal quality information, the MCE or BM-SC may determine that the eNB 804 c should be part of the multicast broadcast service area 812 and/or be a part of an MBSFN area within the multicast broadcast service area 812. The MCE or BM-SC may make such a determination based on providing MBSFN (MBMS) services for any UEs served by the eNB 804 c, such as the UE 826, or based on providing improved (e.g., improved RSRP, RSRQ, RSSI, SINR) MBSFN services for any UEs on the cell edge of the eNB 804 c, such as for the UEs 820, 822. Specifically, the MCE or BM-SC may determine based on the UE count information that a sufficient number of UEs within the coverage of the eNB 804 c, such as the UE 826, would like to receive MBSFN services from the eNB 804 c. Furthermore, the MCE or BM-SC may determine based on the UE count information that a sufficient number of UEs, such as the UEs 820, 822, reported a signal quality from the eNB 802 b less than a first quality threshold and a signal quality from the eNB 804 c greater than a second quality threshold. The MCE or BM-SC may then determine that the UEs 820, 822 are on the edge of the cells between the eNBs 802 b, 804 c, and may therefore benefit from receiving MBSFN services from the eNB 804 c.

As shown in FIG. 8, the cells 802 (i.e., the set of cells 814) within the multicast broadcast service area 812 are statically configured and therefore the multicast broadcast service area configuration and the MBSFN area of each of the cells 802 may not be adapted or changed dynamically. However, the cells 804, 806, 808, 810 (i.e., the set of cells 816) within the multicast broadcast service area 812 are adaptively configured and therefore the multicast broadcast service area configuration and/or the MBSFN area of each of the cells 804, 806, 808, 810 may be adapted or changed dynamically. Upon receiving the UE count information and the signal quality information, the MCE or BM-SC may rank the adaptively configured eNBs 816 based on the UE count information and the signal quality information. For example, the MCE or BM-SC may rank an adaptively configured eNB higher if the adaptively configured eNB serves a sufficient number of UEs that would like to receive MBSFN services and/or would improve the signal quality of a sufficient number of UEs on a cell edge of the adaptively configured eNB. In one configuration, the eNBs within the multicast broadcast service area 812 perform the ranking and send ranked list information to the MCE or BM-SC. Based on the ranked adaptively configured eNBs 816, the MCE or BM-SC determines which eNBs should be part of the multicast broadcast service area 812 and/or part of particular MBSFN areas. The MCE or BM-SC then sends information to the eNBs indicating whether the eNBs should be part of the multicast broadcast service area 812 and/or particular MBSFN areas.

The MCE or BM-SC may also determine a broadcasting tier for the eNB upon determining the eNB should be part of the multicast broadcast service area 812 and/or particular MBSFN areas. The broadcasting tier may be a first tier (tier 1) 840 for broadcasting a system information block (SIB) indicating an MCCH configuration for the MCCH; a second tier (tier 2) 842 for broadcasting the SIB indicating the MCCH configuration for the MCCH and broadcasting the MCCH indicating an MTCH configuration; or a third tier (tier 3) 844 for broadcasting the SIB indicating the MCCH configuration for the MCCH, broadcasting the MCCH indicating the MTCH configuration, and broadcasting the MTCH. The tiers allow for particular adaptive eNBs to be configured to provide different levels of MBSFN services. For example, if an adaptive eNB serves many UEs interested in receiving MBSFN services or the broadcasting of the MTCH would improve cell edge UEs served by other eNBs, the adaptive eNB may be configured in tier 3. However, if the adaptive eNB serves few or no UEs and the broadcasting of the MTCH would provide no to little improvement to cell edge UEs served by other eNBs, the adaptive eNB may be configured in tier 2 or tier 1. As shown in FIG. 8, based on the UE count information and the signal quality information, the MCE or BM-SC determined that the eNBs 804 a, 804 b, 804 c should provide tier 3 844 MBSFN services, the eNB 806 a should provide tier 2 842 MBSFN services, the eNB 808 a should provide tier 1 840 MBSFN services, and the eNB 810 a should not be a part of the multicast broadcast service area 812 and/or provide MBSFN services (846). Upon determining the broadcasting tier for the eNBs, the MCE or BM-SC sends information to the eNBs indicating their MBSFN broadcasting tier.

When the MCE/BM-SC determines that an adaptive eNB should not be a part of the multicast broadcast service area 812, the multicast broadcast service area decreases in size. When the MCE/BM-SC determines that an adaptive eNB should be a part of the multicast broadcast service area 812, the multicast broadcast service area increases in size. As such, the determination of whether adaptive eNBs should be part of the multicast broadcast service area 812 ultimately changes the size of the multicast broadcast service area 812, usually on the edges of the multicast broadcast service area 812. As discussed supra, each multicast broadcast service area 812 may support up to eight MBSFN areas. When the MCE/BM-SC determines that an adaptive eNB should not be a part of an MBSFN area of the multicast broadcast service area 812, the multicast broadcast service area 812 may not change in size. Instead, the services provided by one of the cells in the multicast broadcast service area 812 changes. The adaptive multicast broadcast service area and adaptive MBSFN areas allow for areas associated with MBSFN/MBMS services to change based on UE mobility, UE multicast broadcast service interest, multicast broadcast reception quality improvement, etc.

FIG. 9 is a diagram 900 illustrating a first exemplary architecture for adaptively configuring multicast broadcast service areas/MBSFN areas. UEs are instructed by serving eNBs to measure and to report measurement report messages (MRMs) about the serving eNB and surrounding/neighboring eNBs. The UEs may also report on whether they would like to receive MBSFN services or particular MBSFN services. The UEs send the information within the input I1 to the eNBs. The input I1 includes MRMs and information for obtaining a count of UEs (i.e., UE count information) interested in MBSFN services or particular MBSFN services. The MRMs may include radio frequency (RF) results, such as RSRP, RSRQ, RSSI, or SINR measurements. The MRMs may further include a list of cells (e.g., physical cell identities (PCIs)). The eNBs receive the input I1 from the UEs.

In logical function LF1, the eNBs may extract RF measurements, obtain the list of cells, and determine a count of UEs (i.e., UE count information) that would like to receive MBSFN services or particular MBSFN services. The eNBs may then rank the list of cells. In the logical function LF2, the eNBs may transmit elaborated information to the MCE and receive an updated configuration for the multicast broadcast service area and/or MBSFN areas. The elaborated information may include the RF measurements, list of cells, and the UE count information. Alternatively or additionally, the elaborated information may include the ranked list of cells. The eNBs send input I2 to the MCE. The input I2 includes candidate neighbors, including RF statistics and observed sets. In logical function LF3, the MCE receives the list information, executes MBSFN area optimization algorithms to maximize a goal function for adjusting to the network load and MBMS user distribution, and transmits updated cluster sets (i.e., multicast broadcast service area and/or MBSFN area configurations) back to the eNBs indicating whether the eNBs should be part of the multicast broadcast service area and/or part of particular MBSFN areas.

FIG. 10 is a diagram 1000 illustrating a first exemplary signaling design for an adaptive MBSFN. As shown in FIG. 10, in step 1002, the MME sends a session start request to the MCE. In step 1004, the MCE responds by sending a session start response to the MME. In step 1006, the MCE sends an M2 interface setup request to the eNB1. In step 1008, the eNB1 responds by sending an M2 interface setup response to the MCE. In step 1010, in response to receiving the M2 setup request, the eNB1 obtains UE measurement reports and UE count information indicating a number of UEs served by the eNB1 that are interested in receiving MBSFN services and/or particular MBSFN services, and sends the UE measurement reports and UE count information to the MCE. Based on the received information, the MCE then determines whether particular eNBs should be part of the multicast broadcast service area and/or part of particular MBSFN areas. In step 1012, the MCE sends an MCE configuration update to the eNB1 and receives an MCE configuration update response from the eNB1. In step 1014, the MCE sends MBMS scheduling information to the eNB1. The MBMS scheduling information may include an MBSFN area identifier (ID), PMCH configuration information, and a reserved cell indication. The MCE may send information, explicitly or implicitly, to the eNB1 indicating an adapted MBSFN configuration in relation to the multicast broadcast service area and/or MBSFN areas within the MCE configuration update in step 1012 or the MBMS scheduling information in step 1014. In one configuration, the adaptive MBSFN configuration information may be sent, explicitly or implicitly, within the M2 setup request in step 1006, assuming the measurement report and counting procedures of step 1010 is performed before step 1006. In another configuration, the adaptive MBSFN configuration information may be sent, explicitly or implicitly, within an eNB configuration update acknowledgment. In step 1016, the eNB1 sends an MBMS scheduling information response to the MCE. In step 1018, the MCE sends a session start request to the eNB1. In step 1020, the MCE receives a session start response from the eNB1. In step 1022, the MCE repeats steps 1006 through 1016 with the eNB2. In step 1024, the MCE may receive UE count information from the MME in a backend counting procedure in which UE count information is received from the MME. The MCE may use the UE count information from the eNBs and/or the MME when determining the adaptive MBSFN configuration for each of the adaptive eNBs.

FIG. 11 is a diagram 1100 illustrating a second exemplary signaling design for an adaptive MBSFN. As shown in FIG. 11, in step 1102, the eNB1 sends an M2 interface setup request to the MCE. In step 1104, the MCE responds by sending an M2 interface setup response to the eNB1. In step 1106, the MCE may send an MCE configuration update to the eNB1. The MCE may send the MCE configuration update to the eNB1 with an empty Cell Information List Information Element (IE) if the MCE does not want the eNB1 to send MCCH/MTCH. In step 1108, the eNB1 sends an MCE configuration update response to the MCE. In step 1110, the MCE may repeat steps 1102 to 1108 for the eNB2. In step 1112, the MME sends a session start request to the MCE. In step 1114, the MCE responds by sending a session start response to the MME. In step 1116, the eNB1 and eNB2 obtain UE measurement reports and UE count information indicating a number of UEs served by the eNB1 and eNB2, respectively, that are interested in receiving MBSFN services and/or particular MBSFN services, and send the UE measurement reports and UE count information to the MCE. Based on the received information, the MCE then determines whether particular eNBs should be part of the multicast broadcast service area and/or part of particular MBSFN areas. In step 1018, the MCE sends an MCE configuration update to the eNB1. The MCE configuration update may change the multicast broadcast service area and/or particular MBSFN areas of the eNB1. In step 1120, the MCE receives an MCE configuration update response from the eNB1. In step 1122, the MCE sends MBMS scheduling information to the eNB1. The MBMS scheduling information may include an MBSFN area ID, PMCH configuration information, and a reserved cell indication. The MCE may signal to the eNB1 that the eNB1 should not broadcast MCCH/MTCH through the reserved cell indication by informing the eNB1 that it is a reserved cell. In step 1124, the eNB1 sends an MBMS scheduling information response to the MCE. In step 1126, the MCE sends a session start request to the eNB1. In step 1128, the eNB1 sends a session start response to the MCE. In step 1130, the MCE may repeat the steps 1116 to 1128 with the eNB2.

FIG. 12 is a diagram 1200 illustrating a second exemplary architecture for adaptively configuring multicast broadcast service areas/MBSFN areas. UEs are instructed by serving eNBs to measure and to send UE measurement reports about the serving eNB and surrounding/neighboring eNBs. The UEs may also report on whether they would like to receive MBSFN services or particular MBSFN services. The UEs send the information within the input I1 to the eNBs. The input I1 includes MRMs, and may further include information for obtaining a count of UEs (i.e., UE count information) interested in MBSFN services or particular MBSFN services. The MRMs include RF results, such as RSRP, RSRQ, RSSI, or SINR measurements. The MRMs may further include a list of cells (e.g., PCIs). The eNBs receive the input I1 from the UEs.

In logical function LF1, the eNBs extract RF measurements and obtain the list of cells. The eNBs may also determine a count of UEs (i.e., UE count information) that would like to receive MBSFN services or particular MBSFN services. The eNBs may also rank the list of cells. In the logical function LF2, the eNBs transmit elaborated information to the MCE and receive an updated multicast broadcast service area and/or MBSFN area. The elaborated information may include the RF measurements and list of cells. The elaborated information may further include the UE count information. Alternatively or additionally, the elaborated information may include the ranked list of cells if the eNBs rank the cells. The eNBs send input I2 to the MCE. The input I2 includes candidate neighbors, including RF statistics and observed sets. In logical function LF3, the MCE receives the list information, executes MBSFN area optimization algorithms to maximize a goal function for adjusting to the network load and MBMS user distribution, and transmits updated cluster sets (i.e., multicast broadcast service area and/or MBSFN area configurations) back to the eNBs indicating whether the eNBs should be part of the multicast broadcast service area and/or part of particular MBSFN areas. In logical function LF4, the BM-SC detects a high attach rate for (e.g., receiving, desire to receive) the same content from the UEs in the same location. In logical function LF5, the BM-SC determines the multicast broadcast service area and/or particular MBSFN areas for some eNBs and indicates the MBSFN configuration to the MCE through the MBMS Gateway (MBMS-GW) and MME.

FIG. 13 is a diagram 1300 illustrating a third exemplary signaling design for an adaptive MBSFN. As shown in FIG. 13, in step 1302, the BM-SC sends a session start request to the MME. The session start request may include a list of Cell Global Identities (CGIs) defining an adaptive MBSFN configuration and an MBSFN configuration, such as MCCH/MTCH configurations (e.g., a modulation and coding scheme (MCS)). In step 1304, the MME sends a session start response to the BM-SC. In step 1306, the MME sends a session start request to the MCE. In step 1308, the MCE responds by sending a session start response to the MME. In step 1310, the MCE may obtain the UE count information for the BM-SC. In step 1312, the MCE sends an M2 interface setup request to the eNB1. In step 1314, the eNB1 responds by sending an M2 interface setup response to the MCE. In step 1316, the MCE sends MBMS scheduling information to the eNB1. The MBMS scheduling information may include an MBSFN area ID, PMCH configuration information, and a reserved cell indication. In step 1318, the eNB1 sends an MBMS scheduling information response to the MCE. In step 1320, the MCE sends a session start request to the eNB1. In step 1322, the MCE receives a session start response from the eNB1. In step 1324, the MCE repeats steps 1304 through 1314 with the eNB2. In step 1326, the BM-SC may obtain UE count information (see LF4 of FIG. 12). In step 1328, the BM-SC may also obtain UE measurement reports. Based on the UE count information and the UE measurement reports, the BM-SC may determine an adaptive MBSFN configuration for configuring particular eNBs to be part of the multicast broadcast service area and/or particular MBSFN areas. In step 1330, the BM-SC sends a session update request to the MME. The session update request includes a list of CGIs defining the determined adaptive MBSFN configuration and an MBSFN configuration. In step 1332, the MME sends a session update response to the BM-SC. In step 1334, the MME sends a session update request to the MCE. The session update request includes the adaptive MBSFN configuration. In step 1336, the MCE sends a session update response to the MME. In step 1338, the MCE sends a session update request to the eNB1. The session update request includes the adaptive MBSFN configuration. In step 1340, the eNB1 sends a session start response to the MCE.

Adaptive MBSFN, discussed supra in relation to FIGS. 8-13, may be applied to PTT/PTX. PTT/PTX may be provided through unicast transmissions or multicast/broadcast transmissions through eMBMS. Providing PTT/PTX through unicast channels may not be efficient for a large target group of UEs. Furthermore, eMBMS may be too slow for some types of communication. There is currently a need for MBMS bearer enhancements for PTT/PTX in order to reduce call latency. Furthermore, there is a need for service discovery and security enhancements when PTT/PTX is provided through eMBMS.

FIG. 14 is a diagram 1400 illustrating PTT/PTX through eMBMS. As shown in FIG. 14, a PTT over cellular (PoC) server 1402 receives an IP packet from a UE 1410 (also referred to as a PoC originator) from a unicast channel through an eNB, packet data network gateway (P-GW)/(server gateway) SGW. The PoC server 1402 sends a unicast IP packet to a BM-SC 1404 over an IP Multimedia Subsystem (IMS) (also referred to as IP Multimedia Core Network Subsystem). The IMS is an architectural framework for delivering IP multimedia services. The BM-SC 1404 sends the IP packet (referred to now a multicast/broadcast IP packet) through an SG-imb interface to an MBMS-GW 1406. The MBMS-GW 1406 forwards the multicast/broadcast IP packet through an M1 interface to an eNB 1408. The signaling is between the BM-SC 1404 and the MBMS-GW 1406 through an SGmb interface, between the MBMS-GW 1406 and an MME through an Sm interface, between the MME and the MCE 1408 through an M3 interface, and between the MCE 1408 and the eNB 1408 through an M2 interface. The eNB 1408 broadcasts the multicast/broadcast IP packet to the UEs 1412 (also referred to as a PoC target) as an eMBMS service in an MTCH.

FIG. 15 is a diagram 1500 illustrating a first call flow using an MBMS bearer. In a first step, the UE 1502 performs a unicast traffic channel (TCH) setup with the eNB/MME 1504. In the unicast TCH setup, the UE 1502 sends the eNB/MME 1504 an RRC connection request/service request, the eNB/MME 1504 sends an RRC connection setup response to the UE 1502, the UE sends an RRC connection setup complete message to the eNB/MME 1504, and the UE 1502 sends an RRC reconfiguration complete message to the eNB/MME 1504 when the unicast TCH setup is complete. The eNB/MME 1504 subsequently sends a modify bearer request to the P-GW/SGW 1506. The P-GW/SGW 1506 responds with a modify bearer response. In a second step, the UE 1502 sends a session initiation protocol (SIP) invitation request to the eNB/MME 1504. The SIP invitation request is routed to a PoC server 1514 through the P-GW/SGW 1506 and a SIP proxy 1512. The SIP invitation request may include a group uniform resource locator (URL) and/or a group list of targets. The SIP invitation request may further include a UE capability. The UE capability may indicate whether the UE supports receiving communication through MBMS bearers, group bearers, or both MBMS and group bearers. In a third step, the PoC server may 1514 locate target(s) or contact a home subscriber server (HSS) and/or an authentication, authorization, and accounting (AAA) server for authentication. In addition, the PoC server 1514 may assign a TMGI for the PTT/PTX communication originating from the UE 1502. The PoC server 1514 may contact the BM-SC 1510 to obtain the TMGI and/or security key (e.g., an MBMS session key (MSK)) for the communication. The PoC server 1514 may forward the SIP invitation request to other PoC servers. In a fourth step, the PoC server 1514 sends a SIP invitation response (also referred to as a 1xx response) to the UE 1502. The SIP invitation response may be routed through the SIP proxy 1512, the P-GW/SGW 1506, and the eNB/MME 1504. After the fourth step, a PoC server that received the SIP invitation request from the PoC server 1514 may set up the PoC targets. In a fifth step, the PoC server 1514 sends a session description protocol (SDP) offer (also referred to as a 200 OK response) to the UE 1502. The PoC server 1514 received the SDP offer from a target UE or from another PoC server associated with the target UE. The SDP offer may be routed through the SIP proxy 1512 and the P-GW/SGW 1506. The SDP offer may include one or more of a multicast IP address/port, a TMGI, and an MSK protected by an MBMS user key (MUK). The MSK may be used to generate an MBMS traffic key (MTK). The time that is taken between the start of the first step and the completion of the fifth step is an initial PTT latency 1516. In a sixth step, the UE 1502 acknowledges the SDP offer by sending an SDP answer to the eNB 1504, which may be routed to the PoC server 1514 through the P-GW/SGW 1506 and the SIP proxy 1512. In a seventh step, the PoC server 1514 may inform the UE 1502 via a talk burst confirm message that the UE 1502 may now send data/media via the PTT/PTX provided through eMBMS. In an eighth step, the UE 1502 sends the data/media to the eNB 1504, which may be routed to the PoC server 1514 through the P-GW/SGW 1506.

FIG. 16 is a diagram 1600 illustrating a second call flow using an MBMS bearer. A PoC server 1602 receives the SIP invitation request from the PoC server 1514. The SIP invitation request includes the SDP offer. As discussed supra, the SDP offer may include one or more of a multicast IP address/port, the assigned TMGI, and an MSK. In a first step, the PoC server 1602 sends the SIP invitation request to a SIP proxy 1604. In addition, a BM-SC 1606 performs an eMBMS session setup and provides the assigned TMGI for the PTT/PTX data/media to an MBMS-GW 1608, which provides the assigned TMGI to an MME/MCE 1612, which provides the assigned TMGI to an eNB 1614. The SIP proxy 1604 responds to the PoC server 1602 with a SIP invitation response. In a second step, the PoC server 1602 sends the SIP invitation request to a P-GW/SGW 1610. The SIP invitation request is routed through the SIP proxy 1604. The SIP invitation request may include the SDP offer. The P-GW/SGW 1610 sends a DL data notification including the assigned TMGI to the MME/MCE 1612. The eNB 1614 sends a paging message (which may be a group paging message) to the target UEs, including the target UE (PoC target) 1616. Based on the received paging message, the UE 1616 performs a unicast TCH setup with the eNB 1614. The MME/MCE 1612 sends a modify bearer request to the P-GW/SGW 1610. The P-GW/SGW 1610 responds to the MME/MCE 1612 with a modify bearer response. The P-GW/SGW 1610 forwards a SIP invitation request to the UE 1616. The SIP invitation request includes the SDP offer, which includes the TMGI and the MSK. In a third step, the UE 1616 may receive a user service description (USD). In a fourth step, the UE 1616 receives the MCCH and tunes to the MTCH corresponding to the received TMGI. In a fifth step, the UE 1616 sends an SDP answer (also referred to as a 200 OK response) to the PoC server 1602. The SDP answer is routed to the PoC server 1602 through the eNB 1614, the P-GW/SGW 1610, and the SIP proxy 1604. The PoC server 1602 sends the SDP answer to the PoC server 1514, which forwards the SDP answer to the UE 1502. In a sixth step, the PoC server 1602 acknowledges by sending an SDP answer to the UE 1616. The SDP answer is routed through the SIP proxy 1604, the P-GW/SGW 1610, and the eNB 1614. In a seventh step, the PoC server 1602 sends a talker identity to the UE 1616. The talker identity is an identity of the user of the UE 1502. The talker identity is routed through the P-GW/SGW 1610, the MME/MCE 1612, and the eNB 1614. The eNB 1614 may send the talker identity through the eMBMS resources. In an eighth step, the PoC server 1602 readdresses received PTT/PTX data/media to be multicasted. In a ninth step, the PoC server 1602 sends the received PTT/PTX data/media to the UE 1616. The PTT/PTX data/media is routed through the BM-SC 1606, the MBMS-GW 1608, and the eNB 1614, which sends the PTT/PTX data media through eMBMS on the MTCH corresponding to the assigned TMGI.

Service Discovery Enhancement

In one configuration, a group or an MBMS user service may be preconfigured. For each prearranged group, the eMBMS system may pre-assign a unique multicast IP address/port and a TMGI. One or more TMGIs can be pre-allocated. For PTX, one TMGI may be used for all file downloading. A file delivery table (FDT) instance of a scheduling fragment may be used by a UE for determining the files to be downloaded by the UE. UEs may be aware of the MBMS user service identifier (ID) or the TMGI(s) associated with the group addresses, along with other group information for the groups of which the UEs are a member. The MBMS user service ID may be used to hide transport details from a UE. eMBMS middleware may manage transport details with a service announcement file. When MBMS is preconfigured, the MBMS is effectively always on, and the BM-SC 1606 does not perform the eMBMS session setup step.

If TMGIs are not pre-allocated for PTT/PTX (e.g., the group or the MBMS user service is not pre-configured) (see FIGS. 15, 16), such as in an adhoc group call, group call setup signaling may be used (e.g., the SIP signaling provided with respect to FIGS. 15, 16). As discussed in relation to FIGS. 15, 16, the group call setup signaling may include MBMS session information, such as the MBMS user service name, TMGI, SDP, USD, etc. A group call server may use the MBMS bearer for a large group and interfaces with a BM-SC to initiate the MBMS session. A UE may acquire service information through the group call setup signaling. Group paging may be used. A TMGI or an MBMS user service ID may be included in a paging message. Referring to FIG. 16, the paging message from the eNB 1614 to the UE 1616 may be a group paging message that includes a TMGI and/or an MBMS user service ID.

Minimize Call Latency

Call latency may be on the order of seconds for PTT/PTX through an MBMS bearer. Call latency should preferably be less than 300 ms. In one configuration, the MBMS bearer may be pre-setup or the MBMS session may be preconfigured to be immediately available. When the MBMS session is not being used for a group call, the resources may be allocated to unicast traffic. In one configuration, call latency may be reduced by reducing an LTE radio interface call setup time. In one configuration, the target radio interface call setup may be performed in parallel with the originator call setup interface (see FIGS. 17, 18). In this configuration, PTT call setup signaling (e.g., SIP invitation request) may be piggybacked in a RACH, RRC connection setup request, or RRC connection setup complete. In one configuration, a group ID, a TMGI, or an MBMS service ID may be included in a paging message. In one configuration, group call setup signaling (e.g., SIP signaling) may include MBMS session information, such as an MBMS user service name, TMGI, SDP, USD, etc. In one configuration, call latency may be reduced by not setting up the unicast channel on call setup SIP signaling for target UEs (see FIG. 18). SIP signaling may be sent over MBMS to all target UEs. SIP signaling may be sent to a preconfigured MBMS bearer. An MBMS group key (MGK) may be needed to protect MSK sent to the UEs. A UE may get the MGK when the UE is registered in a group with the network. A fake 200 OK message may be sent to the originator UE from a PoC/group call server if the group size is sufficiently large. Call latency may be reduced by using one or more of the aforementioned configurations.

FIG. 17 is a diagram 1700 illustrating a first parallel call setup. In FIG. 17, call latency may be reduced by performing a parallel call setup. As shown in FIG. 17, in order to reduce call latency, the UE 1702 may include the SIP invitation request to the eNB/MME 1704 within an RRC connection setup message during unicast TCH setup. The eNB/MME 1704 may forward the SIP invitation request through a modify bearer request to the P-GW/SGW 1706, which may forward the SIP invitation request to the PoC server 1714 through the SIP proxy 1712. The PoC server 1714 may assign a TMGI or obtain a TMGI from the BM-SC 1710. The PoC server 1714 may send the SIP invitation request to the PoC server 1716 while the UE 1702 is performing unicast TCH setup. The SIP invitation request may include an SDP offer, the assigned TMGI, and an MSK. The SDP offer may itself include the assigned TMGI and the MSK. The PoC server 1716 establishes an MBMS session with the BM-SC 1720 and provides the assigned TMGI and the MSK to the BM-SC 1720. The BM-SC 1720 performs an eMBMS session setup and provides the assigned TMGI for the PTT/PTX data/media to an MBMS-GW 1722, which provides the assigned TMGI to an MME/MCE 1726, which provides the assigned TMGI to an eNB 1728. The PoC server 1716 sends the SIP invitation request to the SIP proxy 1718. The SIP proxy 1718 sends the SIP invitation request to a P-GW/SGW 1724. The SIP invitation request may include the SDP offer, the assigned TMGI, and the MSK. The P-GW/SGW 1724 sends a DL data notification including the assigned TMGI to the MME/MCE 1726. The eNB 1728 sends a paging message (which may be a group paging message) to the target UEs, including the target UE 1730. Based on the received paging message, the UE 1730 performs a unicast TCH setup with the eNB 1728. The UE 1730 receives a SIP invitation request in an RRC connection setup message during the unicast TCH setup. The SIP invitation request includes the assigned TMGI. The MME/MCE 1726 sends a modify bearer request to the P-GW/SGW 1724. The P-GW/SGW 1724 responds to the MME/MCE 1726 with a modify bearer response. The UE 1730 receives the MCCH and tunes to the MTCH corresponding to the received TMGI. Thereafter, the UE 1730 sends an SDP answer to the UE 1702. The UE 1702 acknowledges by sending an SDP answer to the UE 1730. The PoC server 1714 sends a talk burst confirm message granting the UE 1702 permission to send PTT/PTX data/media to the target UE 1730. The PoC server 1714 sends a talker identity to the UE 1730. Thereafter, the UE 1702 sends the PTT/PTX data/media to the UE 1730. The UE 1702 sends the PTT/PTX data/media to the network through a unicast bearer. The network sends the PTT/PTX data/media to the UE 1730 through an MBMS bearer.

FIG. 18 is a diagram 1800 illustrating a second parallel call setup. In FIG. 18, call latency may be reduced by performing a parallel call setup and removing the requirement that the target UEs perform a unicast TCH setup. As shown in FIG. 18, in order to reduce call latency, the UE 1802 may include the SIP invitation request to the eNB/MME 1804 within an RRC connection setup message during unicast TCH setup. The eNB/MME 1804 may forward the SIP invitation request through a modify bearer request to the P-GW/SGW 1806, which forwards the SIP invitation request to the PoC server 1814 through the MBMS-GW 1808, the BM-SC 1810, and the SIP proxy 1812. The PoC server 1814 may assign a TMGI or obtain a TMGI from the BM-SC 1810. The PoC server 1814 may send the SIP invitation request to the PoC server 1816 while the UE 1802 is still performing unicast TCH setup. The SIP invitation request may include an SDP offer, the assigned TMGI, and an MSK. The MSK may be protected by an MBMS group key (MGK). The SDP offer may itself include the assigned TMGI and the MSK. The PoC server 1816 establishes an MBMS session with the BM-SC 1820 and provides the assigned TMGI or a different TMGI and the MSK to the BM-SC 1820. The BM-SC 1820 performs an eMBMS session setup and provides the received TMGI for receiving a SIP invitation request to an MBMS-GW 1822, which provides the TMGI to an MME/MCE 1826, which provides the TMGI to an eNB 1828. The eNB 1828 pages the target UEs 1830 and includes information indicating the TMGI within the paging message or includes information within the paging message that allows the target UEs 1830 to obtain the TMGI. The PoC server 1816 sends the SIP invitation request through the SIP proxy 1818 to the BM-SC 1820. The SIP invitation request includes the assigned TMGI. The BM-SC 1820 sends the SIP invitation request to the eNB 1828. The SIP invitation request may include the SDP offer, the assigned TMGI, and the MSK. The UEs 1830 receive the MCCH and tune to the MTCH corresponding to the received TMGI in order to receive a SIP invitation request. Thereafter, the eNB 1828 sends the SIP invitation request to the UEs 1830. The SIP invitation request may include the SDP offer, the assigned TMGI, and the MSK. The UEs 1830 receive the MCCH and tune to the MTCH corresponding to the assigned TMGI in order to receive the PTT/PTX data/media. The PoC server 1816 sends a fake 200 OK message to the PoC server 1814. The PoC server 1814 sends an SDP offer to the UE 1802. The UE 1802 acknowledges by sending an SDP answer to the UEs 1830. The PoC server 1814 sends a talk burst confirm message granting the UE 1802 permission to send PTT/PTX data/media to the target UEs 1830. The PoC server 1814 sends a talker identity to the UEs 1830. Thereafter, the UE 1802 sends the PTT/PTX data/media to the UEs 1830. The different MBMS bearers and TMGIs may be used for sending the call control signaling, talk burst control signaling, and PTT/PTX data/media. If same MBMS bearer and associated TMGI is used for sending the call control signaling, talk burst control signaling, and PTT/PTX data/media, FDT or other in-band signaling may be used to distinguish them.

Talk Burst Control Signaling

Talk burst control messages (e.g., the talk burst confirm messages of FIGS. 15-18) may be used to ensure that only one user is given a permission to speak while all other users listen. Talk burst control messages may be sent between a PoC server and originator and target UEs. A talk burst control message can be carried in user datagram protocol (UDP) based signaling with a specified special UDP port. A talk burst control message may be carried in real-time transport protocol (RTP) Control Protocol (RTCP) messages if RTP over MBMS is used. If dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) is used over MBMS, a talk burst control message may be carrier in extended SIP signaling, open mobile alliance (OMA) signaling, an HTTP extension, or FDT based signaling. The talk burst control message may be sent via MBMS or a shared channel if the message is sent to all listeners. The talker identity and a no talk indication may also be sent via MBMS or a shared channel. If queuing is supported, the PoC server may indicate permission to all listeners on the floor. Permission may be divided in time among different UEs in the queue.

FIG. 19 is a diagram 1900 for illustrating security enhancements with an MBMS bearer for PTT/PTX. In a first configuration, MTKs used for PTT/PTX data/media are generated by the UE (PoC Talker) 1902. The MTK used for talk burst control signaling is generated by the PoC server 1904. The PoC server 1904, upon receiving an MTK protected by an MSK and an MTK ID, sends the MTK protected by an MSK and MTK ID to a BM-SC. In a second configuration, the BM-SC generates MTKs and sends the MTKs, protected by an MSK, to the originator and target UEs through in-band signaling. Referring to FIG. 19, when a UE 1902 wants to initiate PTT/PTX communication, the UE 1902 generates a first MTK, referred to as an MTK1, and an ID for the MTK1, referred to as MTK1_ID. The MTK1 is protected based on an MSK and the MTK1_ID. The UE 1902 encrypts a talk burst request message based on the MTK1. In a first step, the UE 1902 sends the talk burst request to a PoC server 1904. The PoC server 1904 generates a second MTK, referred to as MTK2, and an ID for the MTK2, referred to as MTK2_ID. The MTK2 is protected based on the MSK and the MTK2_ID. The PoC server 1904 encrypts a talk burst granted message based on the MTK2. In a second step, the PoC server 1904 sends the talk burst granted message to the UE 1902. The PoC server 1904 encrypts a talker identity based on the MTK2. In a third step, the PoC server 1904 sends the talker identity to a target UE 1906. The UE 1902 generates a third MTK, referred to as an MTK3, and an ID for the MTK3, referred to as MTK3_ID. The MTK3 is protected based on the MSK and the MTK3_ID. The UE 1902 encrypts PTT/PTX data/media based on the MTK3. In a fourth step, the UE 1902 sends the PTT/PTX data/media protected by MTK3 to the UEs 1906 through the PoC server BM-SC.

Adaptive SFN, discussed in relation to FIGS. 8-13, may be utilized in relation to providing PTT/PTX through MBMS bearers. When an MBMS bearer is used, a group ID, a TMGI, or an MBMS user service ID may be used for paging. A UE and radio access network (RAN) capability may be reported to the PoC server. When a UE is moved in and out from an MBMS bearer area, the UE may notify the network or the network may handoff the UE to a proper channel.

FIG. 20 is a flow chart 2000 of a method of wireless communication. The method may be performed by a UE. The UE performs a PTT/PTX call setup for communication via MBMS. In step 2002, the UE performs the PTT/PTX call setup by setting up a unicast bearer with an eNB. In step 2004, the UE includes group call setup signaling to the eNB while setting up the unicast bearer. After setting up the unicast bearer, in step 2006, the UE may receive a talk burst control message from the eNB through an MBMS bearer. Subsequently, in step 2008, the UE may send PTT/PTX data to be transmitted to one or more target UEs over an MBMS bearer.

The group call setup signaling may include service announcement and discovery information for an MBMS bearer. The group call setup signaling may be a SIP invitation request. The SIP invitation request may include a list of target UEs. A UE may set up the unicast bearer by sending an RRC connection request, receiving an RRC connection setup response, and sending an RRC connection complete message. The group call setup signaling may be sent with the RRC connection complete message. For example, referring to FIG. 17, the RRC connection setup complete message sent during unicast TCH setup by the UE 1702 to the eNB 1704 includes a SIP invitation request.

In step 2006, a UE may receive a talk burst control message through an MBMS bearer. In step 2006, the talk burst control message may include at least one of an indication that PTT/PTX communication can be sent, an indication that PTT/PTX communication cannot be sent, or scheduling information for indicating when PTT/PTX communication can be sent. The talk burst control message may be received through one of a UDP, a SIP, an HTTP, an FDT instance, or OMA signaling. For example, referring to FIG. 17, the UE 1702 receives a talk burst confirm message granting the UE 1702 the floor, i.e., the permission to send the PTT/PTX data/media.

A UE may send a first talk burst control message encrypted based on a first set of MTKs. In addition, the UE may receive a second talk burst control message encrypted based on a second set of MTKs different than the first set of MTKs. Furthermore, the UE may send PTT/PTX data on an MBMS bearer based on a third set of MTKs different than the first set of MTKs and the second set of MTKs. For example, referring to FIG. 19, in a first step, the UE 1902 sends a first talk burst control message encrypted based on a first set of MTKs including MTK1. In addition, in a second step, the UE 1902 receives a second talk burst control message encrypted based on a second set of MTKs including MTK2. The second set of MTKs is different than the first set of MTKs. Furthermore, in a fourth step, the UE 1902 sends PTT/PTX data based on a third set of MTKs including MTK3. The third set of MTKs is different than the first set of MTKs and the second set of MTKs.

In step 2008, the UE sends PTT/PTX data to be transmitted to one or more target UEs over an MBMS bearer. For example, referring to FIG. 17, the UE 1702 sends PTT/PTX data to be transmitted to the target UE 1730 over an MBMS bearer. For another example, referring to FIG. 19, the UE 1902 sends PTT/PTX data to be transmitted to the target UE 1906 over an MBMS bearer.

FIG. 21 is a conceptual data flow diagram 2100 illustrating the data flow between different modules/means/components in an exemplary apparatus 2102. The apparatus may be a UE. The UE performs a PTT/PTX call setup for communication via MBMS. The UE includes a unicast bearer setup module 2114 that is configured to set up a unicast bearer with an eNB 2150. The unicast bearer setup module 2114 communicates with a receiving module 2110 and a transmission module 2116 in order to perform the unicast bearer setup. The UE includes a group call setup signaling module 2112 that is configured to send group call setup signaling to the eNB while setting up the unicast bearer.

The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow chart of FIG. 20 and the diagrams of FIGS. 14-19. As such, each step in the aforementioned figures may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 22 is a diagram 2200 illustrating an example of a hardware implementation for an apparatus 2102′ employing a processing system 2214. The processing system 2214 may be implemented with a bus architecture, represented generally by the bus 2224. The bus 2224 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 2214 and the overall design constraints. The bus 2224 links together various circuits including one or more processors and/or hardware modules, represented by the processor 2204, the modules 2110, 2112, 2114, 2116, and the computer-readable medium 2206. The bus 2224 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 2214 may be coupled to a transceiver 2210. The transceiver 2210 is coupled to one or more antennas 2220. The transceiver 2210 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 2210 receives a signal from the one or more antennas 2220, extracts information from the received signal, and provides the extracted information to the processing system 2214. In addition, the transceiver 2210 receives information from the processing system 2214, and based on the received information, generates a signal to be applied to the one or more antennas 2220. The processing system 2214 includes a processor 2204 coupled to a computer-readable medium 2206. The processor 2204 is responsible for general processing, including the execution of software stored on the computer-readable medium 2206. The software, when executed by the processor 2204, causes the processing system 2214 to perform the various functions described supra for any particular apparatus. The computer-readable medium 2206 may also be used for storing data that is manipulated by the processor 2204 when executing software. The processing system further includes at least one of the modules 2110, 2112, 2114, 2116. The modules may be software modules running in the processor 2204, resident/stored in the computer readable medium 2206, one or more hardware modules coupled to the processor 2204, or some combination thereof. The processing system 2214 may be a component of the UE 650 and may include the memory 660 and/or at least one of the TX processor 668, the RX processor 656, and the controller/processor 659.

In one configuration, the apparatus 2102/2102′ for wireless communication includes means for setting up a unicast bearer with an eNB, and means for sending group call setup signaling to the eNB while setting up the unicast bearer. The apparatus may further include means for receiving a talk burst control message through an MBMS bearer. The apparatus may further include means for sending a first talk burst control message encrypted based on a first set of MTKs, means for receiving a second talk burst control message encrypted based on a second set of MTKs different than the first set of MTKs, and means for sending PTT/PTX data based on a third set of MTKs different than the first set of MTKs and the second set of MTKs. The apparatus may further includes means for sending PTT/PTX data to be transmitted to one or more target UEs over an MBMS bearer. The aforementioned means may be one or more of the aforementioned modules of the apparatus 2102 and/or the processing system 2214 of the apparatus 2102′ configured to perform the functions recited by the aforementioned means. As described supra, the processing system 2214 may include the TX Processor 668, the RX Processor 656, and the controller/processor 659. As such, in one configuration, the aforementioned means may be the TX Processor 668, the RX Processor 656, and the controller/processor 659 configured to perform the functions recited by the aforementioned means.

FIG. 23 is a flow chart 2300 of a method of wireless communication. The method may be performed by a UE. The UE performs a PTT/PTX call setup for communication via MBMS. In step 2302, the UE sets up a unicast bearer with an eNB. In step 2304, the UE receives group call setup signaling from the eNB while setting up the unicast bearer. In step 2306, the UE may receive a talk burst control message through an MBMS bearer. In step 2308, the UE may receive PTT/PTX data over an MBMS bearer.

The group call setup signaling may be service announcement and discovery information for an MBMS bearer. The group call setup signaling may include a SIP invitation request. A UE may set up the unicast bearer by sending an RRC connection request, receiving an RRC connection setup response, and sending an RRC connection complete message. A UE may receive the group call setup signaling with the RRC connection setup response. For example, referring to FIG. 17, the UE 1730 receives a SIP invitation request with an RRC connection setup response.

In step 2306, a UE receives a talk burst control message through an MBMS bearer. The talk burst control message may be at least one of an identity of a user sending the PTT/PTX communication or scheduling information for indicating when PTT/PTX communication is received. A UE may receive the talk burst control message through one of a UDP, a SIP, an HTTP, an FDT instance, or OMA signaling. For example, referring to FIG. 17, the UE 1730 receives a talker identity in talk burst control message.

In one configuration, a session of the MBMS is always on with a preconfigured TMGI or MBMS user service identifier. Referring to FIG. 17, in such a configuration, the MBMS session establish step by the PoC server 1716 and the eMBMS session setup step by the BM-SC 1720 are not performed.

In one configuration, in step 2306, a UE receives a talk burst control message encrypted based on a first set of MTKs. In step 2308, the UE receives PTT/PTX data on an MBMS bearer based on a second set of MTKs different than the first set of MTKs. For example, referring to FIG. 19, the UE 1906 receives a talk burst control message encrypted based on a first set of MTKs including MTK2. The UE receives PTT/PTX data on an MBMS bearer based on a second set of MTKs including MTK3. The second set of MTKs is different than the first set of MTKs. Referring to FIG. 17, the talk burst control message encrypted based on MTK2 may be a talker identity, for example.

FIG. 24 is a conceptual data flow diagram 2400 illustrating the data flow between different modules/means/components in an exemplary apparatus 2402. The apparatus may be a UE. The UE performs a PTT/PTX call setup for communication via MBMS. The UE includes a unicast bearer setup module 2414 that is configured to set up a unicast bearer with an eNB 2450. The unicast bearer setup module 2414 communicates with a receiving module 2410 and a transmission module 2416 in order to perform the unicast bearer setup. The UE includes a group call setup signaling module 2412 that is configured to receive group call setup signaling from the eNB while setting up the unicast bearer.

The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow chart of FIG. 23 and the diagrams of FIGS. 14-19. As such, each step in the aforementioned figures may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 25 is a diagram 2500 illustrating an example of a hardware implementation for an apparatus 2402′ employing a processing system 2514. The processing system 2514 may be implemented with a bus architecture, represented generally by the bus 2524. The bus 2524 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 2514 and the overall design constraints. The bus 2524 links together various circuits including one or more processors and/or hardware modules, represented by the processor 2504, the modules 2410, 2412, 2414, 2416, and the computer-readable medium 2506. The bus 2524 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 2514 may be coupled to a transceiver 2510. The transceiver 2510 is coupled to one or more antennas 2520. The transceiver 2510 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 2510 receives a signal from the one or more antennas 2520, extracts information from the received signal, and provides the extracted information to the processing system 2514. In addition, the transceiver 2510 receives information from the processing system 2514, and based on the received information, generates a signal to be applied to the one or more antennas 2520. The processing system 2514 includes a processor 2504 coupled to a computer-readable medium 2506. The processor 2504 is responsible for general processing, including the execution of software stored on the computer-readable medium 2506. The software, when executed by the processor 2504, causes the processing system 2514 to perform the various functions described supra for any particular apparatus. The computer-readable medium 2506 may also be used for storing data that is manipulated by the processor 2504 when executing software. The processing system further includes at least one of the modules 2410, 2412, 2414, 2416. The modules may be software modules running in the processor 2504, resident/stored in the computer readable medium 2506, one or more hardware modules coupled to the processor 2504, or some combination thereof. The processing system 2514 may be a component of the UE 650 and may include the memory 660 and/or at least one of the TX processor 668, the RX processor 656, and the controller/processor 659.

In one configuration, the apparatus 2402/2402′ for wireless communication includes means for setting up a unicast bearer with an eNB, and means for receiving group call setup signaling from the eNB while setting up the unicast bearer. The apparatus may further include means for receiving a talk burst control message through an MBMS bearer. The apparatus may further include means for receiving PTT/PTX data over an MBMS bearer. The apparatus may further include means for receiving a talk burst control message encrypted based on a first set of MTKs, and means for receiving PTT/PTX data on an MBMS bearer based on a second set of MTKs different than the first set of MTKs. The aforementioned means may be one or more of the aforementioned modules of the apparatus 2402 and/or the processing system 2514 of the apparatus 2402′ configured to perform the functions recited by the aforementioned means. As described supra, the processing system 2514 may include the TX Processor 668, the RX Processor 656, and the controller/processor 659. As such, in one configuration, the aforementioned means may be the TX Processor 668, the RX Processor 656, and the controller/processor 659 configured to perform the functions recited by the aforementioned means.

FIG. 26 is a flow chart 2600 of a method of wireless communication. The method may be performed by a UE. The UE performs a PTT/PTX call setup for communication via MBMS. In step 2602, the UE receives a group page while in an RRC idle state. In step 2604, the UE receives group call setup signaling based on information in the group page. In step 2606, the UE may receive a talk burst control message through an MBMS bearer. In step 2608, the UE may receive PTT/PTX data on an MBMS bearer.

The group page may include a TMGI. If the group page includes a TMGI, the UE may tune to an MBMS bearer corresponding to the TMGI, and then receive the group call setup signaling on the MBMS bearer. The group call setup signaling may include service announcement and discovery information for an MBMS bearer. The service announcement and discovery information may include a security key. The security key may be an MSK protected by an MGK. The group call setup signaling may be received on an MBMS bearer. The group call setup signaling may include a SIP invitation request. For example, referring to FIG. 18, the UEs 1830 receive a group page with a TMGI. The UEs 1830 receive control information on an MCCH, and tune to an MTCH corresponding to the TMGI. The UEs 1830 then receive a SIP on the MTCH. The SIP may include an SDP offer, a TMGI for receiving a PTT/PTX data/media communication, and an MSK protected by an MSG.

In step 2606, the UE receives a talk burst control message through an MBMS bearer. The talk burst control message may include at least one of an identity of a user sending the PTT/PTX communication or scheduling information for indicating when PTT/PTX communication is received. For example, referring to FIG. 18, the talk burst control message includes a talker identity. The talk burst control message may be received through one of a UDP, a SIP, an HTTP, an FDT instance, or OMA signaling.

In one configuration, a session of the MBMS is always on with a preconfigured TMGI or MBMS user service identifier. For example, referring to FIG. 18, if a session of the MBMS is always on, the PoC server 1816 does not perform the MBMS session establish step, and the BM-SC 1818 does not perform the eMBMS session setup step.

In one configuration, in step 2606, a UE may receive a talk burst control message encrypted based on a first set of MTKs. In step 2608, the UE may receive PTT/PTX data on an MBMS bearer based on a second set of MTKs different than the first set of MTKs. For example, referring to FIG. 19, the UE 1906 receives a talk burst control message encrypted based on a first set of MTKs including MTK2. The UE receives PTT/PTX data on an MBMS bearer based on a second set of MTKs including MTK3. The second set of MTKs is different than the first set of MTKs. Referring to FIG. 18, the talk burst control message encrypted based on MTK2 may be a talker identity, for example.

FIG. 27 is a conceptual data flow diagram 2700 illustrating the data flow between different modules/means/components in an exemplary apparatus 2702. The apparatus may be a UE. The UE performs a PTT/PTX call setup for communication via MBMS. The UE includes a group page processing module 2714 that is configured to receive a group page while in an RRC idle state. The group page processing module 2714 configures the receiving module 2710 to receive group call setup signaling through an MBMS bearer from an eNB 2750. The receiving module 2710 is configured to receive group call setup signaling based on information in the group page. The receiving module 2710 provides the group call setup signaling to a group call setup signaling module 2712. The group call setup signaling module 2712 interfaces with a transmission module 2716, which communicates with the eNB 2750.

The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow chart of FIG. 26 and the diagrams of FIGS. 14-19. As such, each step in the aforementioned figures may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 28 is a diagram 2800 illustrating an example of a hardware implementation for an apparatus 2702′ employing a processing system 2814. The processing system 2814 may be implemented with a bus architecture, represented generally by the bus 2824. The bus 2824 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 2814 and the overall design constraints. The bus 2824 links together various circuits including one or more processors and/or hardware modules, represented by the processor 2804, the modules 2710, 2712, 2714, 2716, and the computer-readable medium 2806. The bus 2824 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 2814 may be coupled to a transceiver 2810. The transceiver 2810 is coupled to one or more antennas 2820. The transceiver 2810 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 2810 receives a signal from the one or more antennas 2820, extracts information from the received signal, and provides the extracted information to the processing system 2814. In addition, the transceiver 2810 receives information from the processing system 2814, and based on the received information, generates a signal to be applied to the one or more antennas 2820. The processing system 2814 includes a processor 2804 coupled to a computer-readable medium 2806. The processor 2804 is responsible for general processing, including the execution of software stored on the computer-readable medium 2806. The software, when executed by the processor 2804, causes the processing system 2814 to perform the various functions described supra for any particular apparatus. The computer-readable medium 2806 may also be used for storing data that is manipulated by the processor 2804 when executing software. The processing system further includes at least one of the modules 2710, 2712, 2714, 2716. The modules may be software modules running in the processor 2804, resident/stored in the computer readable medium 2806, one or more hardware modules coupled to the processor 2804, or some combination thereof. The processing system 2814 may be a component of the UE 650 and may include the memory 660 and/or at least one of the TX processor 668, the RX processor 656, and the controller/processor 659.

In one configuration, the apparatus 2702/2702′ for wireless communication includes means for receiving a group page while in an RRC idle state, and means for receiving group call setup signaling based on information in the group page. The apparatus may further include means for tuning to an MBMS bearer corresponding to the TMGI when the group page includes a TMGI. In such a configuration, the group call setup signaling is received on the MBMS bearer. The apparatus may further include means for receiving a talk burst control message through an MBMS bearer. The apparatus may further include means for receiving PTT/PTX data on an MBMS bearer. The apparatus may further include means for receiving a talk burst control message encrypted based on a first set of MTKs, and means for receiving PTT/PTX data on an MBMS bearer based on a second set of MTKs different than the first set of MTKs. The aforementioned means may be one or more of the aforementioned modules of the apparatus 2702 and/or the processing system 2814 of the apparatus 2702′ configured to perform the functions recited by the aforementioned means. As described supra, the processing system 2814 may include the TX Processor 668, the RX Processor 656, and the controller/processor 659. As such, in one configuration, the aforementioned means may be the TX Processor 668, the RX Processor 656, and the controller/processor 659 configured to perform the functions recited by the aforementioned means.

FIG. 29 is a flow chart 2900 of a method of wireless communication. The method may be performed by a network including one or more network entities. The network performs PTT/PTX call setup for communication via MBMS. In step 2902, the network may setup one or more unicast bearers. In step 2904, the network sets up an MBMS session for PTT/PTX communication for an originating UE and two or more target UEs. In step 2906, the network sends group call setup signaling to the originating UE and the target UEs. The group call setup signaling may be sent through a unicast bearer or an MBMS bearer. In step 2908, the network sends a talk burst control message through an MBMS bearer. In step 2910, the network sends PTT/PTX data, received from the originating UE, over an MBMS bearer to the target UEs. For example, referring to FIG. 17, the network sets up unicast bearers for the UEs 1702, 1730. In addition, the network sets up an MBMS session (see MBMS session establish and eMBMS session setup steps) for PTT/PTX communication for the UEs 1702, 1730. In FIG. 17, the group call setup signaling is sent through a unicast bearer to the UE 1730. However, in FIG. 18, the group call setup signaling is sent through an MBMS bearer to the UEs 1830. The network sends talk burst control messages such as a talk burst confirm and talker identity through an MBMS bearer. Furthermore, the network sends PTT/PTX data, received from the UEs 1702, 1802, on an MBMS bearer to the UEs 1730, 1830, respectively.

The network may receive a list of the target UEs for PTT/PTX communication from the originating UE. With respect to adaptive MBSFNs, the network may determine whether a base station should be part of at least one of a multicast broadcast service area or an MBSFN area based on a location of the originating UE and the target UEs. In addition, the network may send to the base station information indicating whether the base station should be part of the at least one of the multicast broadcast service area or the MBSFN area. The network may setup the MBMS session in the at least one of the multicast broadcast service area or the MBSFN area. The network may modify the at least one of the multicast broadcast service area or the MBSFN area based on count information associated with the target UEs. Count information was discussed supra with respect to FIGS. 8-13.

The group call setup signaling may include service announcement and discovery information for an MBMS bearer. The service announcement and discovery information may include a security key. The security key may be an MSK protected by an MGK. The group call setup signaling may include a SIP invitation request. The group call setup signaling may be sent on an MBMS bearer.

The network may set up a unicast bearer with the target UEs by receiving an RRC connection request, sending an RRC connection setup response, and receiving an RRC connection complete message. The group call setup signaling may be sent with the RRC connection setup response. In step 2908, the network may send a talk burst control message through an MBMS bearer. The talk burst control message may include at least one of an identity of a user sending the PTT/PTX communication or scheduling information for indicating when PTT/PTX communication is received. The talk burst control message may include at least one of an indication that PTT/PTX communication can be sent, an indication that PTT/PTX communication cannot be sent, or scheduling information for indicating when PTT/PTX communication can be sent. The talk burst control message may be sent through one of a UDP, a SIP, an HTTP, an FDT instance, or OMA signaling.

In one configuration, a session of the MBMS is always on with a preconfigured TMGI or MBMS user service identifier. If a session of the MBMS is always on, then the MBMS session establish step and the MBMS session setup step of FIGS. 16, 17, and 18 are not performed.

The network may send a group page to the target UEs. The group page may include a TMGI. The network may send the group call setup signaling on an MBMS bearer corresponding to the TMGI. For example, referring to FIG. 18, the eNB 1828 sends a group page to the UEs 1830. The group page includes a TMGI. The eNB 1828 sends the UEs 1830 group call setup signaling including a SIP on an MBMS bearer corresponding to the TMGI.

In one configuration, the network receives a first talk burst control message from the originating UE. The first talk burst control message is encrypted based on a first set of MTKs. The network sends a second talk burst control message to the originating UE. The second talk burst control message is encrypted based on a second set of MTKs different than the first set of MTKs. The network sends a third talk burst control message to the target UEs. The third talk burst control message is encrypted based on the second set of MTKs. The network receives PTT/PTX data encrypted based on a third set of MTKs different than the first set of MTKs and the second set of MTKs. The network sends the received PTT/PTX data on an MBMS bearer.

FIG. 30 is a conceptual data flow diagram 3000 illustrating the data flow between different modules/means/components in an exemplary apparatus 3002. The apparatus may be a network including one or more network entities. The network includes an MBMS session setup module 3014 that is configured to set up an MBMS session for PTT/PTX communication for an originating UE and target UEs 3050. The MBMS session setup module communicates with a receiving module 3010 and a transmission module 3016 to facilitate the MBMS session setup. The network further includes a group call setup signaling module 3012 that is configured to send group call setup signaling to the originating UE and the target UEs.

The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow chart of FIG. 29 and the diagrams of FIGS. 8-19. As such, each step in the aforementioned figures may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 31 is a diagram 3100 illustrating an example of a hardware implementation for an apparatus 3002′ employing a processing system 3114. The processing system 3114 may be implemented with a bus architecture, represented generally by the bus 3124. The bus 3124 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 3114 and the overall design constraints. The bus 3124 links together various circuits including one or more processors and/or hardware modules, represented by the processor 3104, the modules 3010, 3012, 3014, 3016, and the computer-readable medium 3106. The bus 3124 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 3114 may be coupled to a transceiver 3110. The transceiver 3110 is coupled to one or more antennas 3120. The transceiver 3110 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 3110 receives a signal from the one or more antennas 3120, extracts information from the received signal, and provides the extracted information to the processing system 3114. In addition, the transceiver 3110 receives information from the processing system 3114, and based on the received information, generates a signal to be applied to the one or more antennas 3120. The processing system 3114 includes a processor 3104 coupled to a computer-readable medium 3106. The processor 3104 is responsible for general processing, including the execution of software stored on the computer-readable medium 3106. The software, when executed by the processor 3104, causes the processing system 3114 to perform the various functions described supra for any particular apparatus. The computer-readable medium 3106 may also be used for storing data that is manipulated by the processor 3104 when executing software. The processing system further includes at least one of the modules 3010, 3012, 3014, 3016. The modules may be software modules running in the processor 3104, resident/stored in the computer readable medium 3106, one or more hardware modules coupled to the processor 3104, or some combination thereof.

In one configuration, the apparatus 3002/3002′ for wireless communication includes means for setting up an MBMS session for PTT/PTX communication for an originating UE and target UEs, and means for sending group call setup signaling to the originating UE and the target UEs. The apparatus may further include means for receiving a list of the target UEs for PTT/PTX communication from the originating UE. The apparatus may further include means for determining whether a base station should be part of at least one of a multicast broadcast service area or an MBSFN area based on a location of the originating UE and the target UEs. The apparatus may further include means for sending to the base station information indicating whether the base station should be part of the at least one of the multicast broadcast service area or the MBSFN area. The MBMS session may be set up in the at least one of the multicast broadcast service area or the MBSFN area. The apparatus may further include means for modifying the at least one of the multicast broadcast service area or the MBSFN area based on count information associated with the target UEs. The apparatus may further include means for setting up a unicast bearer with the target UEs by receiving an RRC connection request, sending an RRC connection setup response, and receiving an RRC connection complete message. The group call setup signaling may be sent with the RRC connection setup response. The apparatus may further include means for sending a talk burst control message through an MBMS bearer. The apparatus may further include means for sending PTT/PTX data, received from the originating UE, on an MBMS bearer to the target UEs. The apparatus may further include means for sending a talk burst control message encrypted based on a first set of MTKs, and means for sending PTT/PTX data over MBMS based on a second set of MTKs different than the first set of MTKs. The apparatus may further include mean for sending a group page to the target UEs. The apparatus may further include means for receiving a first talk burst control message from the originating UE. The first talk burst control message may be encrypted based on a first set of MTKs. The apparatus may further include means for sending a second talk burst control message to the originating UE. The second talk burst control message may be encrypted based on a second set of MTKs different than the first set of MTKs. The apparatus may further include means for sending a third talk burst control message to the target UEs. The third talk burst control message may be encrypted based on the second set of MTKs. The apparatus may further include means for receiving PTT/PTX data encrypted based on a third set of MTKs different than the first set of MTKs and the second set of MTKs. The apparatus may further include means for sending the received PTT/PTX data on an MBMS bearer. The aforementioned means may be one or more of the aforementioned modules of the apparatus 3002 and/or the processing system 3114 of the apparatus 3002′ configured to perform the functions recited by the aforementioned means.

FIG. 32 is a diagram 3200 illustrating PTT/PTX through unicast, group, and MBMS bearers. As shown in FIG. 32, a PoC server 3202 receives an IP packet from a UE 3210 from a unicast channel through an eNB, P-GW/SGW. The PoC server 3202 sends a unicast IP packet to a BM-SC 3204 over an IMS. The BM-SC 3204 sends the IP packet (referred to now a multicast/broadcast IP packet) through an SG-imb interface to an MBMS-GW 3206. The MBMS-GW 3206 forwards the multicast/broadcast IP packet through an M1 interface to an eNB 3208. The signaling is between the BM-SC 3204 and the MBMS-GW 3206 through an SGmb interface, between the MBMS-GW 3206 and an MME through an Sm interface, between the MME and the MCE 3208 through an M3 interface, and between the MCE 3208 and the eNB 3208 through an M2 interface. The eNB 3208 broadcasts the multicast/broadcast IP packet to the UEs 3212 as an eMBMS service carried on a corresponding MTCH.

Furthermore, as shown in FIG. 32, the PoC server 3202 sends a unicast IP packet to a P-GW 3220 over an IMS. The P-GW 3220 sends the unicast IP packet to an SGW 3222. The SGW 3222 sends the unicast IP packet to an eNB/MME 3224, which sends the unicast IP packet through a group bearer to the UEs 3226. In addition, the SGW 3222 sends the unicast IP packet to the eNB/MME 3228, which sends the unicast IP packet through a unicast bearer to the UE 3230. In an exemplary configuration, a UE may be able to receive a PTT/PTX communication through a group bearer. A UE may indicate to the network whether the UE is capable of receiving PTT/PTX communication through one or more of a unicast bearer, a group bearer, and an MBMS bearer. When the network receives a PTT/PTX communication, the network may determine whether to utilize unicast, group, and/or MBMS bearers to deliver the PTT/PTX communication. The network may make such a determination based on the bearer capabilities of the target UEs (i.e., intended recipients of the PTT/PTX communication), a number of the target UEs (i.e., a UE group size), whether file repair is needed, the type of the PTT/PTX communication, the importance of the PTT/PTX communication, etc. For example, if the group size is small, the PTT/PTX communication is important, or the PTT/PTX communication may require file repair (e.g., software upgrade), the network may determine to send the PTT/PTX communication through a unicast bearer. For another example, if the group size is large, the PTT/PTX communication is less important, no retransmissions of the PTT/PTX communication are desired, or the PTT/PTX communication is voice or live video, the network may determine to send the PTT/PTX communication through an MBMS bearer. For another example, if the group size is between small and large, the network may determine to send the PTT/PTX communication through a group bearer (or multiple group bearers).

FIG. 33 is a diagram 3300 illustrating a group bearer establishment procedure. In step 0, the PoC/machine type communication (MTC) server receives a group call setup request for a multicast/broadcast data transmission. In one example, the multicast/broadcast data transmission is a PTT/PTX communication. In step 1, the PoC/MTC server sends a group bearer request to a group gateway (Group-GW). The Group-GW queries a home subscriber server (HSS) for serving MMEs of the target UEs and assigns a multicast IP and general packet radio service (GPRS) tunneling protocol user plane (GTP-U) tunnel. In step 2, the Group-GW sends requests to the MMEs to create a group bearer. The requests may include the multicast IP, the GTP-U tunnel information, a group identifier (ID) identifying the group bearer, quality of service (QoS) information, and target UEs. In step 3, each of the MMEs establish group bearers locally, and send a group bearer assignment request to the associated eNBs in order to establish group bearers in the eNBs serving the target UEs. The eNBs establish the group bearer context for the group bearer. The group bearer parameters (also referred to as group bearer context information) include one or more of a bearer ID, the group ID, a group RNTI (G-RNTI), a list of target UEs, an RLC/PDCP configuration, QoS profile, an IP address, and a receiving type. The group bearer parameters may additionally include a discontinuous reception (DRX) configuration. The receiving type, which is discussed further infra, may be one of connected, hybrid, or idle. In step 4, each eNB responds to their associated MME with a group bearer assignment response. In step 5, each eNB sends paging to the group. The paging message includes the G-RNTI, the group ID, and the receiving type. In step 6, if a UE belongs to the group corresponding to the group ID, the UE receives the group bearer parameters in a message on a common control channel (CCCH) or a physical downlink shared channel (PDSCH) from a serving eNB. The message including the group bearer parameters is scrambled based on the G-RNTI. The message further includes information for obtaining the multicast/broadcast data transmission on the PDSCH. In step 7, depending on the receiving type, the target UEs that receive the paging and descramble the message including the group bearer parameters, may enter a connected mode (i.e., an RRC connected state) by a service request procedure, remain in a connected mode, change to an idle mode, or remain in an idle mode. Thereafter, UE group bearer context is established. In step 8, each MME sends a create group bearer response to the Group-GW. In step 9, the Group-GW sends a group bearer response to the PoC/MTC server. Thereafter, the UE may receive the multicast/broadcast data transmission through the established group bearer on the PDSCH from the eNB.

As discussed supra, the receiving type may be connected, hybrid, or idle. If the receiving type is connected, target UEs should be in an RRC connected state to receive the multicast/broadcast data transmission. UEs in an RRC connected state may report CQI to the serving eNB. The serving eNB receives the CQI from the target UEs, determines an MCS based on the received CQI, and sends the multicast/broadcast data transmission at the determined MCS. In a first configuration, the serving eNB determines a worst CQI (i.e., a CQI corresponding to a lowest MCS) and sends the multicast/broadcast data transmission at an MCS corresponding to the worst CQI. Accordingly, all of the target UEs may receive the multicast/broadcast data transmission, as the multicast/broadcast data transmission is sent with an MCS that allows the target UEs with the worst received signal quality to be able to decode successfully the multicast/broadcast data transmission. In a second configuration, the serving eNB determines an MCS that would allow a particular percentage of the target UEs to receive the multicast/broadcast data transmission, and sends the multicast/broadcast data transmission at that MCS. In the second configuration, the serving eNB may send the multicast/broadcast data transmission with a higher MCS than in the first configuration.

If the receiving type is idle, target UEs do not send CQI feedback in relation to the multicast/broadcast data transmission. The target UEs may send CQI feedback for other purposes, such as for example, because the target UEs are in an RRC connected state. That is, if the receiving type is idle, target UEs in an RRC idle state need not change to an RRC connected state to receive the multicast/broadcast data transmission. In addition, target UEs in an RRC connected state need not maintain the RRC connected state to receive the multicast/broadcast data transmission. Furthermore, serving eNBs do not take into account received CQI (e.g., from target UEs in an RRC connected state) when sending the multicast/broadcast data transmission to the target UEs. Serving eNBs may send the multicast/broadcast data transmission at a low MCS or a lowest possible MCS so that a sufficient number of target UEs receive the multicast/broadcast data transmission.

If the receiving type is hybrid (i.e., a hybrid of the idle and connected receiving types), target UEs need not enter an RRC connected state to receive multicast/broadcast data transmission. However, if a target UE has a receiving signal quality less than a signal quality threshold (e.g., RSRP, RSRQ, RSSI, or SINR is less than a threshold), the target UE may enter an RRC connected state in order to provide CQI feedback to the serving eNB. The serving eNB takes into account CQI received from target UEs when determining an MCS for sending the multicast/broadcast data transmission. The serving eNB may indicate the signal quality threshold at which a target UE should enter an RRC connected state within the group bearer parameters (provided in step 6). Accordingly, target UEs with a received signal quality less than the signal quality threshold may enter an RRC connected state, and target UEs with a received signal quality greater than the signal quality threshold need not enter into an RRC connected state. A target UE may use a cell reselection parameter (e.g., Sintersearch) as the signal quality threshold. Even if the receiving signal quality is greater than the signal quality threshold, target UEs may change to an RRC connected state when a cell change is needed (for example, a handover to another cell).

When the receiving type is connected or hybrid and a target UE is in an RRC connected state, the target UE reports CQI, and additionally may report an ACK and/or NACK so that the serving eNB can schedule the group bearer to ensure reception quality. When the serving eNB receives a NACK, the serving eNB re-transmits the multicast/broadcast data transmission packet that was not properly received. Using a packet switched handover (PSHO) procedure, the serving eNB can hand over a UE to a target cell when necessary. As part of the handover, the serving eNB may send the group bearer context information to the target cell. When the receiving type is idle and a UE enters a cell without a current interest in receiving multicast/broadcast data transmission, the UE may initiate a service request procedure to request a group bearer establishment.

With respect to sending ACK/NACKs by the UE, in an implicit ACK/NACK resource mapping rule, all UEs send ACK/NACK on the same resource in UL, which may result in an ACK/NACK collision. A semi-static configuration may be used to specify ACK/NACK resources for each UE. However, when multiple UEs are in the same group, multiple ACK/NACK resources need to be allocated. In one configuration, if one UE within a group fails to receive a multicast/broadcast data transmission packet, the serving eNB will retransmit the multicast/broadcast data transmission packet to all the UEs in the group. The serving eNB may configure UEs to use PUCCH format 1 for sending ACK/NACK. Accordingly, UEs that successfully decode the multicast/broadcast data transmission packet will not ACK, and UEs that fail to decode the multicast/broadcast data transmission packet will send a NACK on the same ACK/NACK resource according to an implicit mapping rule on the first control channel element (CCE) index in the PDCCH associated with the G-RNTI. The ACK/NACK resource may be associated with a PDCCH used for scheduling the multicast/broadcast data transmission. As the NACKs are sent on the same resource, the serving eNB will receive the NACK with an SFN gain when more than one UE transmits the ACK. When the serving eNB receives a NACK, the serving eNB retransmits the multicast/broadcast data transmission packet. If there is DTX on the ACK/NACK resource (i.e., no NACK is received), the serving eNB assumes that all the UEs successfully decoded the multicast/broadcast data transmission packet. The ACK/NACK procedure reduces UL ACK/NACK overhead, as only a single ACK/NACK resource is used per group. Further, NACKs have a SFN gain from multiple users, leading into enhanced ACK/NACK detection.

The ACK/NACK procedure provided supra provides for a more efficient ACK/NACK resource utilization, but with a less efficient retransmission, as a NACK from any UEs in a group with respect to a particular packet results in a retransmission of that particular packet to all the UEs in the group. Alternatively, the serving eNB may utilize network coding ARQ (NC-ARQ) during retransmissions. Accordingly, the retransmission packet may be a function of multiple packets. For example, assume the serving eNB transmits first and second multicast/broadcast data transmission packets, and a first UE is unable to decode successfully the first multicast/broadcast data transmission packet, and the second UE is unable to decode successfully the second multicast/broadcast data transmission packet. The first UE will send a NACK to indicate that the UE was unable to decode the first multicast/broadcast data transmission packet, and the second UE will send a NACK to indicate that the UE was unable to decode the second multicast/broadcast data transmission packet. The serving eNB may combine the first and second multicast/broadcast data transmission packets (e.g., through XOR), and send the combined multicast/broadcast data transmission packet to the first and second UEs. Assume each of the first and second UEs are able to decode the combined multicast/broadcast data transmission packet. The first UE may obtain the first multicast/broadcast data transmission packet based on the second multicast/broadcast data transmission packet and the combined multicast/broadcast data transmission packet, and the second UE may obtain the second multicast/broadcast data transmission packet based on the first multicast/broadcast data transmission packet and the combined multicast/broadcast data transmission packet. As demonstrated in the example, NC-ARQ provides for a more efficient eNB retransmission, but with a less efficient ACK/NACK resource utilization. Utilizing NC-ARQ allows the UE to be aware of ACK/NACK status from each individual UE on an RLC level.

ACK and CQI may be transmitted simultaneously. When a UE in the group needs to transmit ACK and CQI simultaneously, modulated RS may be used for normal CP and joint coding may be used for extended CP. UEs that transmit ACK/NACK and CQI simultaneously do not use a PUCCH format 1 message. With group NACK, UEs within the group send NACK on the same resource if they are not scheduled to send CQI. Otherwise if UEs are scheduled to send CQI, the UEs send individual regular ACK/NACK together with CQI on a corresponding CQI resource. The serving eNB detects ACK/NACK from those UEs that are scheduled to send CQI at the same time. Retransmission depends on group NACK detection in addition to individual ACK/NACK on CQI.

As discussed supra, when UEs are in an RRC connected state, the UEs feedback CQI, and when the receiving type is connected or hybrid, the serving eNB may take into account the received CQI when scheduling the group transmission. For example, the serving eNB may send the multicast/broadcast data transmission based on the worst CQI. In one configuration, UEs need not provide CQI feedback if the CQI is greater than a CQI threshold. In such a configuration, if the serving eNB does not receive CQI feedback, the serving eNB may send the multicast/broadcast data transmission based on an MCS corresponding to the CQI threshold, and if the serving eNB receives CQI feedback, the serving eNB may send the multicast/broadcast data transmission based on the worst CQI feedback. Based on previous CQI feedback and/or a measurement report, a serving eNB may reconfigure UEs with different CQI feedback configurations (e.g., CQI feedback periods). A serving eNB may configure high geometry UEs (i.e., UEs with high signal quality, smaller path loss) to provide CQI feedback less often compared to low geometry UEs (i.e., UEs with a low signal quality, higher path loss). With individual ACK/NACK feedback, the serving eNB can schedule UEs with NACK feedback to transmit CQI and UEs without NACK feedback not to transmit CQI. Multiple UEs may be scheduled for CQI transmissions on the same resource. UEs that fail to decode may transmit CQI and/or UEs that have a CQI lower than the CQI threshold may transmit CQI. UEs may receive the CQI threshold from an eNB in the PDCCH or in an L3 message, such as through RRC signaling.

All UEs within a group bearer can be configured with rank 1 transmissions in which the UEs do not need to send rank information (RI). When multiple UEs are configured in the group bearer, the serving eNB may configure the UEs with a transmit diversity (TxD) mode. In the TxD mode, UEs may use a space-frequency block code (SFBC) with two eNB transmit antennas or SFBC+frequency switched transmit diversity (FSTD) with four eNB transmit antennas to compute CQI feedback. In TxD mode, UEs need not send precoding matrix indicator (PMI) feedback. A serving eNB may schedule (transmit to) UEs using MU-MIMO mode. For MU-MIMO, a UE may compute CQI and PMI and send the CQI/PMI to the serving eNB. ACK/NACK feedback may be according to regular unicast procedure. A UE can further report CQI based on TxD in case the serving eNB cannot pair the UEs in MU-MIMO mode.

With respect to DRX, UEs follow a group DRX configuration when the group bearer is activated. A serving eNB may schedule regular unicast traffic as well as group traffic in the On Duration of the group DRX configuration. PDCCH load may be increased, as the serving eNB may serve more UEs in the On Duration given that all UEs within the same group follow the group DRX configuration. When a group bearer is deactivated, UEs may follow a non-group DRX configuration if configured.

FIG. 34 is a flow chart 3400 of a method of a UE of receiving a multicast/broadcast data transmission via a group bearer. In step 3402, the UE receives a paging message including a type of the group bearer. In step 3404, the UE determines whether to remain in or change to an RRC idle mode or an RRC connected mode based on the type of the group bearer received in the paging message. The type of the group bearer may be one of idle, hybrid, or connected. Specifically, in step 3404, if a UE is in an RRC idle mode, the UE determines whether to remain in the RRC idle mode or change to an RRC connected mode, and if the UE is in an RRC connected mode, the UE determines whether to remain in the RRC connected mode or change to an RRC idle mode. In step 3404, the UE may determine whether to remain in or change to an RRC idle mode or an RRC connected mode based on at least one of a received signal quality, a mobility of the UE, or delay requirements of the multicast/broadcast data transmission when the type of the group bearer is hybrid. The mobility of the UE is whether the UE may move into coverage of other eNBs. If the UE may move into coverage of other eNBs, the UE may determine to remain in or change to an RRC connected mode to take advantage of a handover procedure in the mobility to the new eNB. The delay requirements are allowable time delays associated with the multicast/broadcast data transmission. If the multicast/broadcast data transmission has a short allowable time delay, the UE may remain in or change to an RRC connected mode so that the multicast/broadcast data transmission can be received within the short allowable time delay.

The paging message may further include a group identifier. The UE may subsequently receive group bearer parameters if the UE is associated with the group identifier. The paging message may further include a G-RNTI. The UE may descramble the received group bearer parameters (e.g., received in a PDSCH) based on the G-RNTI. The group bearer parameters may include at least one of a bearer identifier, the group identifier, the G-RNTI, a list of target UEs, an RLC/PDCP configuration, a QoS profile, an IP address, and the type of the group bearer. The group bearer parameters may include a group DRX configuration. The UE may receive the multicast/broadcast data transmission based on the group DRX configuration when the group bearer is activated.

In step 3406, the UE may receive a multicast/broadcast data transmission packet through the group bearer. In step 3408, the UE may send ACK/NACK based on a received ACK/NACK configuration and may send CQI based on a received CQI configuration. In one configuration, the UE attempts to decode the multicast/broadcast data transmission packet, sends a NACK when unable to decode the multicast/broadcast data transmission packet, and refrains from sending an ACK when able to decode the multicast/broadcast data transmission packet. The NACK may be sent in a PUCCH format 1 message. When the UE sends a NACK in a PUCCH format 1 message, the UE is not scheduled to transmit CQI feedback simultaneously with the NACK. The NACK may be sent in a same resource shared by other UEs. The resource may be associated with a PDCCH used for scheduling the multicast/broadcast data transmission.

Upon determining the type of the group bearer, a UE determines whether to remain in an RRC idle mode, change from an RRC idle mode to an RRC connected mode, remain in an RRC connected mode, or change from an RRC connected mode to an RRC idle mode. When the type of the group bearer is hybrid or connected, and the UE determines to provide CQI feedback, the UE determines to remain in or to change to the RRC connected mode. In one configuration, the UE receives a CQI feedback configuration. The CQI feedback configuration may be based on previously provided CQI feedback or a measurement report. The UE sends CQI feedback based on the CQI feedback configuration. In one configuration, the UE receives a multicast/broadcast data transmission packet through the group bearer. The UE attempts to decode the multicast/broadcast data transmission packet, sends CQI feedback when unable to decode the multicast/broadcast data transmission packet, and refrains from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet. In one configuration, the UE determines CQI feedback, sends the CQI feedback when the CQI feedback is less than a CQI threshold, and refrains from sending the CQI feedback when the CQI feedback is greater than the CQI threshold. The UE may receive the CQI threshold through one of a PDCCH or a layer 3 message. The UE may receive the multicast/broadcast data transmission from an eNB, send a NACK upon unsuccessfully decoding the received multicast/broadcast data transmission, and receive a retransmission of the multicast/broadcast data transmission based on NC-ARQ. The UE may receive a configuration to receive the multicast/broadcast data transmission through rank 1 transmissions from an eNB. The UE may determine CQI feedback based on one of an SFBC diversity scheme, or an SFBC and an FSTD diversity scheme, and send the CQI to the eNB. In one configuration, the UE receives a configuration to receive the multicast/broadcast data transmission through MU-MIMO from an eNB, determines CQI feedback and a PMI, and sends the determined CQI and PMI to the eNB.

FIG. 35 is a conceptual data flow diagram 3500 illustrating the data flow between different modules/means/components in an exemplary apparatus 3502. The apparatus 3502 may be a UE. The UE receives a multicast/broadcast data transmission via a group bearer. The UE includes a receiving module 3510 that is configured to receive a paging message including a type of the group bearer. The UE includes an RRC idle/connected mode determination module 3514 that is configured to determine whether to remain in or change to an RRC idle mode or an RRC connected mode based on the type of the group bearer received in the paging message. The type of the group bearer may be one of idle, hybrid, or connected. The RRC idle/connected mode determination module 3514 may determine whether to remain in or change to an RRC idle mode or an RRC connected mode based on at least one of a received signal quality, a mobility of the UE, or delay requirements of the multicast/broadcast data transmission when the type of the group bearer is hybrid. Specifically, if the UE is in an RRC idle mode, the RRC idle/connected mode determination module 3514 determines whether to remain in the RRC idle mode or change to an RRC connected mode, and if the UE is in an RRC connected mode, the RRC idle/connected mode determination module 3514 determines whether to remain in the RRC connected mode or change to an RRC idle mode. The paging message may further include a group identifier. The UE further includes a group bearer processing module 3512 that may determine to receive group bearer parameters if the UE is associated with the group identifier. The paging message may further include a G-RNTI. The group bearer processing module 3512 may be configured to descramble the received group bearer parameters based on the G-RNTI. The receiving module 3510 may be configured to receive a multicast/broadcast data transmission packet through the group bearer. The group bearer processing module 3512 may be configured to attempt to decode the multicast/broadcast data transmission packet. The group bearer processing module 3512 may request a transmission module 3516 to send a NACK when the group bearer processing module 3512 is unable to decode the multicast/broadcast data transmission packet, and request the transmission module 3516 to refrain from sending an ACK when the group bearer processing module 3512 is able to decode the multicast/broadcast data transmission packet. The transmission module 3516 may send the NACK in a PUCCH format 1 message when the UE is not scheduled to transmit CQI feedback simultaneously with the NACK. When the type of the group bearer is hybrid or connected, the RRC idle/connected mode determination module 3514 may determine to remain in or to change to the RRC connected mode. The receiving module 3510 may be configured to receive a CQI feedback configuration and the transmission module 3516 may be configured to send CQI feedback based on the CQI feedback configuration. The receiving module 3510 may be configured to receive a multicast/broadcast data transmission packet, the group bearer processing module 3512 may be configured to attempt to decode the multicast/broadcast data transmission packet, and the transmission module 3516 may be configured to send CQI feedback when the group bearer processing module 3512 is unable to decode the multicast/broadcast data transmission packet, and to refrain from sending the CQI feedback when the group bearer processing module 3512 is able to decode the multicast/broadcast data transmission packet. The group bearer processing module 3512 may be configured to determine CQI feedback and the transmission module 3516 may be configured to send the CQI feedback when the CQI feedback is less than a CQI threshold, and to refrain from sending the CQI feedback when the CQI feedback is greater than the CQI threshold. The receiving module 3510 may be configured to receive the CQI threshold through one of a PDCCH or a layer 3 message (e.g., through RRC signaling). The receiving module 3510 may be configured to receive the multicast/broadcast data transmission from an eNB 3550 and the transmission module 3516 may be configured to send a NACK upon unsuccessfully decoding the received multicast/broadcast data transmission, and to receive a retransmission of the multicast/broadcast data transmission based on NC-ARQ. The receiving module 3510 may be configured to receive a configuration for receiving the multicast/broadcast data transmission through rank 1 transmissions from an eNB 3550. The group bearer processing module 3512 may be configured to determine CQI feedback based on one of an SFBC diversity scheme, or an SFBC and an FSTD diversity scheme, and the transmission module 3516 may be configured to send the CQI feedback to the eNB 3550. The receiving module 3510 may be configured to receive a configuration for receiving the multicast/broadcast data transmission through MU-MIMO from an eNB 3550, the group bearer processing module 3512 may be configured to determine CQI feedback and a PMI, and the transmission module 3516 may be configured to send the determined CQI feedback and PMI to the eNB 3550.

The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow chart of FIG. 34 and the diagrams of FIGS. 8-19. As such, each step in the aforementioned figures may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 36 is a diagram 3600 illustrating an example of a hardware implementation for an apparatus 3502′ employing a processing system 3614. The processing system 3614 may be implemented with a bus architecture, represented generally by the bus 3624. The bus 3624 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 3614 and the overall design constraints. The bus 3624 links together various circuits including one or more processors and/or hardware modules, represented by the processor 3604, the modules 3510, 3512, 3514, 3516, and the computer-readable medium 3606. The bus 3624 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 3614 may be coupled to a transceiver 3610. The transceiver 3610 is coupled to one or more antennas 3620. The transceiver 3610 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 3610 receives a signal from the one or more antennas 3620, extracts information from the received signal, and provides the extracted information to the processing system 3614. In addition, the transceiver 3610 receives information from the processing system 3614, and based on the received information, generates a signal to be applied to the one or more antennas 3620. The processing system 3614 includes a processor 3604 coupled to a computer-readable medium 3606. The processor 3604 is responsible for general processing, including the execution of software stored on the computer-readable medium 3606. The software, when executed by the processor 3604, causes the processing system 3614 to perform the various functions described supra for any particular apparatus. The computer-readable medium 3606 may also be used for storing data that is manipulated by the processor 3604 when executing software. The processing system further includes at least one of the modules 3510, 3512, 3514, 3516. The modules may be software modules running in the processor 3604, resident/stored in the computer readable medium 3606, one or more hardware modules coupled to the processor 3604, or some combination thereof. The processing system 3614 may be a component of the UE 650 and may include the memory 660 and/or at least one of the TX processor 668, the RX processor 656, and the controller/processor 659.

In one configuration, the apparatus 3502/3502′ receives a multicast/broadcast data transmission via a group bearer. The apparatus may be a UE. The UE includes means for receiving a paging message including a type of the group bearer, and means for determining whether to remain in or change to an RRC idle mode or an RRC connected mode based on the type of the group bearer received in the paging message. The paging message may further include a group identifier, and the UE may further include means for receiving group bearer parameters if the UE is associated with the group identifier. The paging message may further include a G-RNTI, and the UE may further include means for descrambling the received group bearer parameters based on the G-RNTI. The group bearer parameters may include a group DRX configuration, and the UE may further include means for receiving the multicast/broadcast data transmission based on the group DRX configuration when the group bearer is activated. The UE may further include means for receiving a multicast/broadcast data transmission packet through the group bearer, means for attempting to decode the multicast/broadcast data transmission packet, means for sending a NACK when unable to decode the multicast/broadcast data transmission packet, and means for refraining from sending an ACK when able to decode the multicast/broadcast data transmission packet. The type of the group bearer may be hybrid or connected, and the UE may further include means for determining to remain in or to change to the RRC connected mode. The UE may further include means for receiving a CQI feedback configuration. The CQI feedback configuration may be based on previously provided CQI feedback or a measurement report. The UE may further include means for sending CQI feedback based on the CQI feedback configuration. The UE may further include means for receiving a multicast/broadcast data transmission packet, means for attempting to decode the multicast/broadcast data transmission packet, means for sending CQI feedback when unable to decode the multicast/broadcast data transmission packet, and means for refraining from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet. The UE may further include means for determining CQI feedback, means for sending the CQI feedback when the CQI feedback is less than a CQI threshold, and means for refraining from sending the CQI feedback when the CQI feedback is greater than the CQI threshold. The UE may further include means for receiving the CQI threshold through one of a PDCCH or a layer 3 message. The UE may further include means for receiving the multicast/broadcast data transmission from an eNB, means for sending a NACK upon unsuccessfully decoding the received multicast/broadcast data transmission, and means for receiving a retransmission of the multicast/broadcast data transmission based on NC-ARQ. The UE may further include means for receiving a configuration to receive the multicast/broadcast data transmission through rank 1 transmissions from an eNB. The UE may further include means for determining CQI feedback based on one of an SFBC diversity scheme, or an SFBC and an FSTD diversity scheme, and means for sending the CQI to the eNB. The UE may further include means for receiving a configuration to receive the multicast/broadcast data transmission through MU-MIMO from an eNB, means for determining CQI feedback and a PMI, and means for sending the determined CQI and PMI to the eNB.

The aforementioned means may be one or more of the aforementioned modules of the apparatus 3502 and/or the processing system 3614 of the apparatus 3502′ configured to perform the functions recited by the aforementioned means. As described supra, the processing system 3614 may include the TX Processor 668, the RX Processor 656, and the controller/processor 659. As such, in one configuration, the aforementioned means may be the TX Processor 668, the RX Processor 656, and the controller/processor 659 configured to perform the functions recited by the aforementioned means.

FIG. 37 is a flow chart 3700 of a method of an eNB of providing a multicast/broadcast data transmission via a group bearer. In step 3702, the eNB determines a type of the group bearer. In step 3704, the eNB sends a paging message including the type of the group bearer to a set of UEs. In step 3702, the eNB may determine the type of the group bearer to be one of idle, hybrid, or connected. The eNB may determine at least one of a type of the multicast/broadcast data transmission, an importance of the multicast/broadcast data transmission, or a number of UEs in the set of UEs. In step 3702, the eNB may determine the type of the group bearer based on the determined at least one of the type of the multicast/broadcast data transmission, the importance of the multicast/broadcast data transmission, or the number of UEs in the set of UEs. The paging message may further include a group identifier associated with the set of UEs. The eNB may send group bearer parameters to the set of UEs. The paging message may further include a G-RNTI. The eNB may scramble the group bearer parameters based on the G-RNTI. The group bearer parameters may include at least one of a bearer identifier, the group identifier, the G-RNTI, a list of UEs in the set of UEs, an RLC/PDCP configuration, a QoS profile, an IP address, and the type of the group bearer. The group bearer parameters may include a group DRX configuration. The eNB may transmit the multicast/broadcast data transmission to the set of UEs based on the group DRX configuration when the group bearer is activated.

In step 3706, the eNB may send an ACK/NACK configuration to the set of UEs for sending ACK/NACK and send a CQI configuration to the set of UEs for sending CQI feedback. In step 3708, the eNB may receive CQI feedback and adjust/determine an MCS for the multicast/broadcast data transmission based on the adjusted MCS. In step 3710, the eNB may send the multicast/broadcast data transmission packet to the set of UEs through the group bearer. In step 3712, the eNB may retransmit the multicast/broadcast data transmission based on a received NACK. In one configuration, the eNB sends a multicast/broadcast data transmission packet to the set of UEs through the group bearer and receives a NACK from each UE in the set of UEs that is unable to decode the multicast/broadcast data transmission packet. In such a configuration, ACKs are not received from UEs in the set of UEs that are able to decode the multicast/broadcast data transmission packet. Each NACK may be received in a PUCCH format 1 message. Each NACK may be received in a same resource shared by each UE in the set of UEs. The resource may be associated with a PDCCH used for scheduling the multicast/broadcast data transmission.

When UEs in the set of UEs send CQI, the eNB may determine the type of the group bearer to be hybrid or connected. The eNB may receive CQI feedback from UEs in the set of UEs that are in an RRC connected mode. In one configuration, the eNB determines an MCS based on the received CQI, and transmits the multicast/broadcast data transmission based on the determined MCS. The eNB may determine the MCS based on a lowest received CQI. In one configuration, the eNB determines a CQI feedback configuration for each UE in the set of UEs based on at least one of CQI feedback or measurement reports received from the UEs, sends the determined CQI feedback configuration to each UE, and receives CQI feedback from each UE in the set of UEs based on the provided CQI feedback configuration. In one configuration, the eNB sends a multicast/broadcast data transmission packet, and configures UEs in the set of UEs to send the CQI feedback when unable to decode the multicast/broadcast data transmission packet and to refrain from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet. In one configuration, the eNB sends a CQI threshold to UEs in the set of UEs, sends a multicast/broadcast data transmission packet, and configures UEs in the set of UEs to send the CQI feedback when CQI is less than the CQI threshold and to refrain from sending the CQI feedback when CQI is greater than the CQI threshold. The eNB may check for a NACK on a CQI resource and an ACK/NACK resource. The ACK/NACK resource is associated with a PDCCH used for scheduling the multicast/broadcast data transmission.

The eNB may send the multicast/broadcast data transmission, receive a NACK with respect to the multicast/broadcast data transmission, and retransmit the multicast/broadcast data transmission based on NC-ARQ. The eNB may send the multicast/broadcast data transmission through a rank 1 transmission. The eNB may send the multicast/broadcast data transmission by utilizing one of an SFBC diversity scheme, or an SFBC and an FSTD diversity scheme. The eNB may send the multicast/broadcast data transmission to the set of UEs through MU-MIMO.

FIG. 38 is a conceptual data flow diagram 3800 illustrating the data flow between different modules/means/components in an exemplary apparatus 3802. The apparatus 3802 may be an eNB that provides a multicast/broadcast data transmission via a group bearer. The eNB may include a receiving module 3810, a group bearer processing module 3812, an MCS determination module 3814, and a transmission module 3816. The group bearer processing module 3812 may be configured to determine a type of the group bearer. The transmission module 3816 may be configured to send a paging message including the type of the group bearer to a set of UEs 3850. The type of the group bearer may be determined to be one of idle, hybrid, or connected. The group bearer processing module 3812 may be configured to determine at least one of a type of the multicast/broadcast data transmission, an importance of the multicast/broadcast data transmission, or a number of UEs in the set of UEs. The group bearer processing module 3812 may be configured to determine the type of the group bearer based on the determined at least one of the type of the multicast/broadcast data transmission, the importance of the multicast/broadcast data transmission, or the number of UEs in the set of UEs. The paging message may further include a group identifier associated with the set of UEs. The transmission module 3816 may be configured to send group bearer parameters to the set of UEs. The paging message may further include a G-RNTI. The group bearer processing module 3812 may be configured to scramble the group bearer parameters based on the G-RNTI. The group bearer parameters may include a group DRX configuration. The transmission module 3816 may be configured to transmit the multicast/broadcast data transmission to the set of UEs based on the group DRX configuration when the group bearer is activated. The transmission module 3816 may be configured to send a multicast/broadcast data transmission packet to the set of UEs through the group bearer, and the receiving module 3810 may be configured to receive a NACK from each UE in the set of UEs that is unable to decode the multicast/broadcast data transmission packet. ACKs may not be received from UEs in the set of UEs that are able to decode the multicast/broadcast data transmission packet. Each NACK may be received in a PUCCH format 1 message. Each NACK may be received in a same resource shared by each UE in the set of UEs. The resource may be associated with a PDCCH used for scheduling the multicast/broadcast data transmission. When the type of the group bearer is determined to be hybrid or connected, the receiving module 3810 may be configured to receive CQI feedback from UEs in the set of UEs that are in an RRC connected mode. The MCS determination module 3814 may be configured to determine an MCS based on the received CQI, and the transmission module 3816 may be configured to transmit the multicast/broadcast data transmission based on the determined MCS. The MCS may be determined based on a lowest received CQI. The group bearer processing module 3812 may be configured to determine a CQI feedback configuration for each UE in the set of UEs based on at least one of CQI feedback or measurement reports received from the UE, the transmission module 3816 may be configured to send the determined CQI feedback configuration to each UE, and the receiving module 3810 may be configured to receive CQI feedback from each UE in the set of UEs based on the provided CQI feedback configuration. The transmission module 3816 may be configured to send a multicast/broadcast data transmission packet, and to configure UEs in the set of UEs to send the CQI feedback when unable to decode the multicast/broadcast data transmission packet and to refrain from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet. The transmission module 3816 may be configured to send a CQI threshold to UEs in the set of UEs, to send a multicast/broadcast data transmission packet, and to configure UEs in the set of UEs to send the CQI feedback when CQI is less than the CQI threshold and to refrain from sending the CQI feedback when CQI is greater than the CQI threshold. The receiving module 3810 and the group bearer processing module 3812 may be configured to check for a NACK on a CQI resource and an ACK/NACK resource. The ACK/NACK resource is associated with a PDCCH used for scheduling the multicast/broadcast data transmission. The transmission module 3816 may be configured to send the multicast/broadcast data transmission, the receiving module 3810 may be configured to receive a NACK with respect to the multicast/broadcast data transmission, and the transmission module 3816 may be configured to retransmit the multicast/broadcast data transmission based on NC-ARQ. The transmission module 3816 may be configured to send the multicast/broadcast data transmission through a rank 1 transmission. The multicast/broadcast data transmission may be sent by utilizing one of an SFBC diversity scheme, or an SFBC and an FSTD diversity scheme. The transmission module 3816 may be configured to send the multicast/broadcast data transmission to the set of UEs through MU-MIMO.

The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow chart of FIG. 37 and the diagrams of FIGS. 8-19. As such, each step in the aforementioned figures may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 39 is a diagram 3900 illustrating an example of a hardware implementation for an apparatus 3802′ employing a processing system 3914. The processing system 3914 may be implemented with a bus architecture, represented generally by the bus 3924. The bus 3924 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 3914 and the overall design constraints. The bus 3924 links together various circuits including one or more processors and/or hardware modules, represented by the processor 3904, the modules 3810, 3812, 3814, 3816, and the computer-readable medium 3906. The bus 3924 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 3914 may be coupled to a transceiver 3910. The transceiver 3910 is coupled to one or more antennas 3920. The transceiver 3910 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 3910 receives a signal from the one or more antennas 3920, extracts information from the received signal, and provides the extracted information to the processing system 3914. In addition, the transceiver 3910 receives information from the processing system 3914, and based on the received information, generates a signal to be applied to the one or more antennas 3920. The processing system 3914 includes a processor 3904 coupled to a computer-readable medium 3906. The processor 3904 is responsible for general processing, including the execution of software stored on the computer-readable medium 3906. The software, when executed by the processor 3904, causes the processing system 3914 to perform the various functions described supra for any particular apparatus. The computer-readable medium 3906 may also be used for storing data that is manipulated by the processor 3904 when executing software. The processing system further includes at least one of the modules 3810, 3812, 3814, 3816. The modules may be software modules running in the processor 3904, resident/stored in the computer readable medium 3906, one or more hardware modules coupled to the processor 3904, or some combination thereof. The processing system 3914 may be a component of the eNB 610 and may include the memory 676 and/or at least one of the TX processor 616, the RX processor 670, and the controller/processor 675.

In one configuration, the apparatus 3802/3802′ provides a multicast/broadcast data transmission via a group bearer. The apparatus may be an eNB. The eNB includes means for determining a type of the group bearer, and means for sending a paging message including the type of the group bearer to a set of UEs. The eNB may further include means for determining at least one of a type of the multicast/broadcast data transmission, an importance of the multicast/broadcast data transmission, or a number of UEs in the set of UEs. The type of the group bearer may be determined based on the determined at least one of the type of the multicast/broadcast data transmission, the importance of the multicast/broadcast data transmission, or the number of UEs in the set of UEs. The paging message may further include a group identifier associated with the set of UEs. The eNB may further include means for sending group bearer parameters to the set of UEs. The paging message may further include a G-RNTI. The eNB may further include means for scrambling the group bearer parameters based on the G-RNTI. The group bearer parameters may include a group DRX configuration. The eNB may further include means for transmitting the multicast/broadcast data transmission to the set of UEs based on the group DRX configuration when the group bearer is activated. The eNB may further include means for sending a multicast/broadcast data transmission packet to the set of UEs through the group bearer, and means for receiving a NACK from each UE in the set of UEs that is unable to decode the multicast/broadcast data transmission packet. The ACKs may not be received from UEs in the set of UEs that are able to decode the multicast/broadcast data transmission packet. The type of the group bearer may be determined to be hybrid or connected, and the eNB may further include means for receiving CQI feedback from UEs in the set of UEs that are in an RRC connected mode. The eNB may further include means for determining an MCS based on the received CQI, and means for transmitting the multicast/broadcast data transmission based on the determined MCS. The eNB may further include means for determining a CQI feedback configuration for each UE in the set of UEs based on at least one of CQI feedback or measurement reports received from the UE, means for sending the determined CQI feedback configuration to each UE, and means for receiving CQI feedback from each UE in the set of UEs based on the provided CQI feedback configuration. The eNB may further include means for sending a multicast/broadcast data transmission packet, and means for configuring UEs in the set of UEs to send the CQI feedback when unable to decode the multicast/broadcast data transmission packet and to refrain from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet. The eNB may further include means for sending a CQI threshold to UEs in the set of UEs, means for sending a multicast/broadcast data transmission packet, and means for configuring UEs in the set of UEs to send the CQI feedback when CQI is less than the CQI threshold and to refrain from sending the CQI feedback when CQI is greater than the CQI threshold. The eNB may further include means for checking for a NACK on a CQI resource and an ACK/NACK resource. The ACK/NACK resource may be associated with a PDCCH used for scheduling the multicast/broadcast data transmission. The eNB may further include means for sending the multicast/broadcast data transmission, means for receiving a NACK with respect to the multicast/broadcast data transmission, and means for retransmitting the multicast/broadcast data transmission based on NC-ARQ. The eNB may further include means for sending the multicast/broadcast data transmission through a rank 1 transmission. The eNB may further include means for sending the multicast/broadcast data transmission to the set of UEs through MU-MIMO.

The aforementioned means may be one or more of the aforementioned modules of the apparatus 3802 and/or the processing system 3914 of the apparatus 3802′ configured to perform the functions recited by the aforementioned means. As described supra, the processing system 3914 may include the TX Processor 616, the RX Processor 670, and the controller/processor 675. As such, in one configuration, the aforementioned means may be the TX Processor 616, the RX Processor 670, and the controller/processor 675 configured to perform the functions recited by the aforementioned means.

FIG. 40 is a flow chart 4000 of a method of PTT/PTX communication. The method may performed by an eNB and/or a network entity. In step 4002, the eNB receives a PTT/PTX message for a set of UEs. In step 4004, the eNB establishes one of a unicast bearer, a group bearer, or an MBMS bearer based on at least one of the PTT/PTX message or the set of UEs. In step 4006, the eNB sends the PTT/PTX message through the established bearer to the set of UEs. The eNB (or another network entity) may determine whether to establish the unicast bearer, the group bearer, or the MBMS bearer based on at least one of bearer capabilities of UEs in the set of UEs, a number of UEs in the set of UEs, whether file repair is needed for the PTT/PTX communication, a type of the PTT/PTX communication, or an importance of the PTT/PTX communication. If a network entity makes such a determination, the network entity may inform the eNB of the determination.

For a particular PTT/PTX communication to a set of UEs, multiple different bearers may be established by the network. For example, assume a set of target UEs includes a first subset in the coverage of a first eNB, a second subset in the coverage of a second eNB, and a third subset in the coverage of a third eNB. The first eNB establishes one of a unicast bearer, a group bearer, or an MBMS bearer, the second eNB establishes one of a unicast bearer, a group bearer, or an MBMS bearer, and the third eNB establishes one of a unicast bearer, a group bearer, or an MBMS bearer. The first, second, and third eNBs may establish different types of bearers based on bearer capabilities of UEs in the corresponding subset of UEs, a number of UEs in the corresponding subset of UEs, whether file repair is needed for the PTT/PTX communication, a type of the PTT/PTX communication, or an importance of the PTT/PTX communication.

FIG. 41 is a conceptual data flow diagram 4100 illustrating the data flow between different modules/means/components in an exemplary apparatus 4102. The apparatus 4102 is configured to determine a bearer for PTT/PTX communication and to establish the bearer for the PTT/PTX communication. The apparatus includes a receiving module 4110 that is configured to receive a PTT/PTX message from a UE 4140 for a set of UEs 4150. The apparatus 4102 includes a bearer processing module 4112 that is configured to establish one of a unicast bearer, a group bearer, or an MBMS bearer based on at least one of the PTT/PTX message or the set of UEs. The apparatus 4102 includes a transmission module 4116 that is configured to send the PTT/PTX message through the established bearer to the set of UEs. The apparatus 4102 further includes a bearer determination module 4114 that is configured to determine whether to establish the unicast bearer, the group bearer, or the MBMS bearer based on at least one of bearer capabilities of UEs in the set of UEs, a number of UEs in the set of UEs, whether file repair is needed for the PTT/PTX communication, a type of the PTT/PTX communication, or an importance of the PTT/PTX communication.

The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow chart of FIG. 40 and the diagrams of FIGS. 8-19. As such, each step in the aforementioned figures may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 42 is a diagram 4200 illustrating an example of a hardware implementation for an apparatus 4102′ employing a processing system 4214. The processing system 4214 may be implemented with a bus architecture, represented generally by the bus 4224. The bus 4224 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 4214 and the overall design constraints. The bus 4224 links together various circuits including one or more processors and/or hardware modules, represented by the processor 4204, the modules 4110, 4112, 4114, 4116, and the computer-readable medium 4206. The bus 4224 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 4214 may be coupled to a transceiver 4210. The transceiver 4210 is coupled to one or more antennas 4220. The transceiver 4210 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 4210 receives a signal from the one or more antennas 4220, extracts information from the received signal, and provides the extracted information to the processing system 4214. In addition, the transceiver 4210 receives information from the processing system 4214, and based on the received information, generates a signal to be applied to the one or more antennas 4220. The processing system 4214 includes a processor 4204 coupled to a computer-readable medium 4206. The processor 4204 is responsible for general processing, including the execution of software stored on the computer-readable medium 4206. The software, when executed by the processor 4204, causes the processing system 4214 to perform the various functions described supra for any particular apparatus. The computer-readable medium 4206 may also be used for storing data that is manipulated by the processor 4204 when executing software. The processing system further includes at least one of the modules 4110, 4112, 4114, 4116. The modules may be software modules running in the processor 4204, resident/stored in the computer readable medium 4206, one or more hardware modules coupled to the processor 4204, or some combination thereof. The processing system 4214 may be a component of the eNB 610 and may include the memory 676 and/or at least one of the TX processor 616, the RX processor 670, and the controller/processor 675.

In one configuration, the apparatus 4102/4102′ is for PTT/PTX communication and includes means for receiving a PTT/PTX message for a set of UEs, means for establishing one of a unicast bearer, a group bearer, or an MBMS bearer based on at least one of the PTT/PTX message or the set of UEs, and means for sending the PTT/PTX message through the established bearer to the set of UEs. The apparatus may further include means for determining whether to establish the unicast bearer, the group bearer, or the MBMS bearer based on at least one of bearer capabilities of UEs in the set of UEs, a number of UEs in the set of UEs, whether file repair is needed for the PTT/PTX communication, a type of the PTT/PTX communication, or an importance of the PTT/PTX communication.

The aforementioned means may be one or more of the aforementioned modules of the apparatus 4102 and/or the processing system 4214 of the apparatus 4102′ configured to perform the functions recited by the aforementioned means. As described supra, the processing system 4214 may include the TX Processor 616, the RX Processor 670, and the controller/processor 675. As such, in one configuration, the aforementioned means may be the TX Processor 616, the RX Processor 670, and the controller/processor 675 configured to perform the functions recited by the aforementioned means.

It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Further, some steps may be combined or omitted. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “at least one of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “at least one of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.” 

What is claimed is:
 1. A method of a user equipment (UE) of receiving a multicast/broadcast data transmission via a group bearer, comprising: receiving a paging message comprising a type of the group bearer; and determining whether to remain in or change to a radio resource control (RRC) idle mode or an RRC connected mode based on the type of the group bearer received in the paging message.
 2. The method of claim 1, wherein the type of the group bearer is one of idle, hybrid, or connected.
 3. The method of claim 2, wherein the determining whether to remain in or change to an RRC idle mode or an RRC connected mode is further based on at least one of a received signal quality, a mobility of the UE, or delay requirements of the multicast/broadcast data transmission when the type of the group bearer is hybrid.
 4. The method of claim 1, wherein the paging message further comprises a group identifier, and the method further comprises receiving group bearer parameters if the UE is associated with the group identifier.
 5. The method of claim 4, wherein the paging message further comprises a group radio network temporary identifier (G-RNTI), and the method further comprises descrambling the received group bearer parameters based on the G-RNTI.
 6. The method of claim 4, wherein the group bearer parameters comprise at least one of a bearer identifier, the group identifier, the G-RNTI, a list of target UEs, a radio link control (RLC)/packet data convergence protocol (PDCP) configuration, a quality of service (QoS) profile, an Internet Protocol (IP) address, and the type of the group bearer.
 7. The method of claim 4, wherein the group bearer parameters comprise a group discontinuous reception (DRX) configuration, and the method further comprises receiving the multicast/broadcast data transmission based on the group DRX configuration when the group bearer is activated.
 8. The method of claim 1, further comprising: receiving a multicast/broadcast data transmission packet through the group bearer; attempting to decode the multicast/broadcast data transmission packet; sending a negative acknowledgement (ACK) (NACK) when unable to decode the multicast/broadcast data transmission packet; and refraining from sending an ACK when able to decode the multicast/broadcast data transmission packet.
 9. The method of claim 8, wherein the NACK is sent in a PUCCH format 1 message.
 10. The method of claim 9, wherein the UE is not scheduled to transmit channel quality indicator (CQI) feedback simultaneously with the NACK.
 11. The method of claim 8, wherein the NACK is sent in a same resource shared by other UEs, wherein the resource is associated with a physical downlink control channel (PDCCH) used for scheduling the multicast/broadcast data transmission.
 12. The method of claim 1, wherein the type of the group bearer is hybrid or connected, and the method further comprises determining to remain in or to change to the RRC connected mode.
 13. The method of claim 12, further comprising: receiving a channel quality indicator (CQI) feedback configuration, the CQI feedback configuration being based on previously provided CQI feedback or a measurement report; and sending CQI feedback based on the CQI feedback configuration.
 14. The method of claim 12, further comprising: receiving a multicast/broadcast data transmission packet; attempting to decode the multicast/broadcast data transmission packet; sending channel quality indicator (CQI) feedback when unable to decode the multicast/broadcast data transmission packet; and refraining from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet.
 15. The method of claim 12, further comprising: determining channel quality indicator (CQI) feedback; sending the CQI feedback when the CQI feedback is less than a CQI threshold; and refraining from sending the CQI feedback when the CQI feedback is greater than the CQI threshold.
 16. The method of claim 15, further comprising receiving the CQI threshold through one of a physical downlink control channel (PDCCH) or a layer 3 message.
 17. The method of claim 1, further comprising: receiving the multicast/broadcast data transmission from an evolved Node B (eNB); sending a negative acknowledgement (NACK) upon unsuccessfully decoding the received multicast/broadcast data transmission; and receiving a retransmission of the multicast/broadcast data transmission based on network coding automatic repeat request (NC-ARQ).
 18. The method of claim 1, further comprising receiving a configuration to receive the multicast/broadcast data transmission through rank 1 transmissions from an evolved Node B (eNB).
 19. The method of claim 18, further comprising: determining channel quality indictor (CQI) feedback based on one of a space-frequency block code (SFBC) diversity scheme, or an SFBC and a frequency switched transmit diversity (FSTD) diversity scheme; and sending the CQI to the eNB.
 20. The method of claim 1, further comprising: receiving a configuration to receive the multicast/broadcast data transmission through multi-user multiple input multiple output (MU-MIMO) from an evolved Node B (eNB); determining channel quality indicator (CQI) feedback and a precoding matrix indicator (PMI); and sending the determined CQI and PMI to the eNB.
 21. A method of an evolved Node B (eNB) of providing a multicast/broadcast data transmission via a group bearer, comprising: determining a type of the group bearer; and sending a paging message comprising the type of the group bearer to a set of user equipments (UEs).
 22. The method of claim 21, wherein the type of the group bearer is determined to be one of idle, hybrid, or connected.
 23. The method of claim 21, further comprising determining at least one of a type of the multicast/broadcast data transmission, an importance of the multicast/broadcast data transmission, or a number of UEs in the set of UEs, wherein the type of the group bearer is determined based on the determined at least one of the type of the multicast/broadcast data transmission, the importance of the multicast/broadcast data transmission, or the number of UEs in the set of UEs.
 24. The method of claim 21, wherein the paging message further comprises a group identifier associated with the set of UEs, and the method further comprises sending group bearer parameters to the set of UEs.
 25. The method of claim 24, wherein the paging message further comprises a group radio network temporary identifier (G-RNTI), and the method further comprises scrambling the group bearer parameters based on the G-RNTI.
 26. The method of claim 24, wherein the group bearer parameters comprise at least one of a bearer identifier, the group identifier, the G-RNTI, a list of UEs in the set of UEs, a radio link control (RLC)/packet data convergence protocol (PDCP) configuration, a quality of service (QoS) profile, an Internet Protocol (IP) address, and the type of the group bearer.
 27. The method of claim 24, wherein the group bearer parameters comprise a group discontinuous reception (DRX) configuration, and the method further comprises transmitting the multicast/broadcast data transmission to the set of UEs based on the group DRX configuration when the group bearer is activated.
 28. The method of claim 21, further comprising: sending a multicast/broadcast data transmission packet to the set of UEs through the group bearer; and receiving a negative acknowledgement (ACK) (NACK) from each UE in the set of UEs that is unable to decode the multicast/broadcast data transmission packet, wherein ACKs are not received from UEs in the set of UEs that are able to decode the multicast/broadcast data transmission packet.
 29. The method of claim 28, wherein each NACK is received in a PUCCH format 1 message.
 30. The method of claim 28, wherein each NACK is received in a same resource shared by each UE in the set of UEs, wherein the resource is associated with a physical downlink control channel (PDCCH) used for scheduling the multicast/broadcast data transmission.
 31. The method of claim 21, wherein the type of the group bearer is determined to be hybrid or connected, and the method further comprises receiving channel quality indicator (CQI) feedback from UEs in the set of UEs that are in a radio resource control (RRC) connected mode.
 32. The method of claim 31, further comprising: determining a modulation and coding scheme (MCS) based on the received CQI; and transmitting the multicast/broadcast data transmission based on the determined MCS.
 33. The method of claim 32, wherein the MCS is determined based on a lowest received CQI.
 34. The method of claim 31, further comprising: determining a channel quality indicator (CQI) feedback configuration for each UE in the set of UEs based on at least one of CQI feedback or measurement reports received from the UE; sending the determined CQI feedback configuration to each UE; and receiving CQI feedback from each UE in the set of UEs based on the provided CQI feedback configuration.
 35. The method of claim 31, further comprising: sending a multicast/broadcast data transmission packet; and configuring UEs in the set of UEs to send the CQI feedback when unable to decode the multicast/broadcast data transmission packet and to refrain from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet.
 36. The method of claim 31, further comprising: sending a CQI threshold to UEs in the set of UEs; sending a multicast/broadcast data transmission packet; and configuring UEs in the set of UEs to send the CQI feedback when CQI is less than the CQI threshold and to refrain from sending the CQI feedback when CQI is greater than the CQI threshold.
 37. The method of claim 31, further comprising checking for a NACK on a CQI resource and an ACK/NACK resource, wherein the ACK/NACK resource is associated with a physical downlink control channel (PDCCH) used for scheduling the multicast/broadcast data transmission.
 38. The method of claim 21, further comprising: sending the multicast/broadcast data transmission; receiving a negative acknowledgement (NACK) with respect to the multicast/broadcast data transmission; and retransmitting the multicast/broadcast data transmission based on network coding automatic repeat request (NC-ARQ).
 39. The method of claim 21, further comprising sending the multicast/broadcast data transmission through a rank 1 transmission.
 40. The method of claim 38, wherein the multicast/broadcast data transmission is sent by utilizing one of a space-frequency block code (SFBC) diversity scheme, or an SFBC and a frequency switched transmit diversity (FSTD) diversity scheme.
 41. The method of claim 21, further comprising sending the multicast/broadcast data transmission to the set of UEs through multi-user multiple input multiple output (MU-MIMO).
 42. A method of push to talk (PTT)/push to everything (PTX) communication, comprising: receiving a PTT/PTX message for a set of user equipments (UEs); establishing one of a unicast bearer, a group bearer, or a Multimedia Broadcast Multicast Service (MBMS) bearer based on at least one of the PTT/PTX message or the set of UEs; and sending the PTT/PTX message through the established bearer to the set of UEs.
 43. The method of claim 42, further comprising determining whether to establish the unicast bearer, the group bearer, or the MBMS bearer based on at least one of bearer capabilities of UEs in the set of UEs, a number of UEs in the set of UEs, whether file repair is needed for the PTT/PTX communication, a type of the PTT/PTX communication, or an importance of the PTT/PTX communication.
 44. An apparatus for receiving a multicast/broadcast data transmission via a group bearer, the apparatus being a user equipment (UE), comprising: means for receiving a paging message comprising a type of the group bearer; and means for determining whether to remain in or change to a radio resource control (RRC) idle mode or an RRC connected mode based on the type of the group bearer received in the paging message.
 45. The apparatus of claim 44, wherein the type of the group bearer is one of idle, hybrid, or connected.
 46. The apparatus of claim 45, wherein the means for determining whether to remain in or change to an RRC idle mode or an RRC connected mode is further based on at least one of a received signal quality, a mobility of the UE, or delay requirements of the multicast/broadcast data transmission when the type of the group bearer is hybrid.
 47. The apparatus of claim 44, wherein the paging message further comprises a group identifier, and the apparatus further comprises means for receiving group bearer parameters if the UE is associated with the group identifier.
 48. The apparatus of claim 47, wherein the paging message further comprises a group radio network temporary identifier (G-RNTI), and the apparatus further comprises means for descrambling the received group bearer parameters based on the G-RNTI.
 49. The apparatus of claim 47, wherein the group bearer parameters comprise at least one of a bearer identifier, the group identifier, the G-RNTI, a list of target UEs, a radio link control (RLC)/packet data convergence protocol (PDCP) configuration, a quality of service (QoS) profile, an Internet Protocol (IP) address, and the type of the group bearer.
 50. The apparatus of claim 47, wherein the group bearer parameters comprise a group discontinuous reception (DRX) configuration, and the apparatus further comprises means for receiving the multicast/broadcast data transmission based on the group DRX configuration when the group bearer is activated.
 51. The apparatus of claim 44, further comprising: means for receiving a multicast/broadcast data transmission packet through the group bearer; means for attempting to decode the multicast/broadcast data transmission packet; means for sending a negative acknowledgement (ACK) (NACK) when unable to decode the multicast/broadcast data transmission packet; and means for refraining from sending an ACK when able to decode the multicast/broadcast data transmission packet.
 52. The apparatus of claim 51, wherein the NACK is sent in a PUCCH format 1 message.
 53. The apparatus of claim 52, wherein the UE is not scheduled to transmit channel quality indicator (CQI) feedback simultaneously with the NACK.
 54. The apparatus of claim 51, wherein the NACK is sent in a same resource shared by other UEs, wherein the resource is associated with a physical downlink control channel (PDCCH) used for scheduling the multicast/broadcast data transmission.
 55. The apparatus of claim 44, wherein the type of the group bearer is hybrid or connected, and the apparatus further comprises means for determining to remain in or to change to the RRC connected mode.
 56. The apparatus of claim 55, further comprising: means for receiving a channel quality indicator (CQI) feedback configuration, the CQI feedback configuration being based on previously provided CQI feedback or a measurement report; and means for sending CQI feedback based on the CQI feedback configuration.
 57. The apparatus of claim 55, further comprising: means for receiving a multicast/broadcast data transmission packet; means for attempting to decode the multicast/broadcast data transmission packet; means for sending channel quality indicator (CQI) feedback when unable to decode the multicast/broadcast data transmission packet; and means for refraining from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet.
 58. The apparatus of claim 55, further comprising: means for determining channel quality indicator (CQI) feedback; means for sending the CQI feedback when the CQI feedback is less than a CQI threshold; and means for refraining from sending the CQI feedback when the CQI feedback is greater than the CQI threshold.
 59. The apparatus of claim 58, further comprising means for receiving the CQI threshold through one of a physical downlink control channel (PDCCH) or a layer 3 message.
 60. The apparatus of claim 44, further comprising: means for receiving the multicast/broadcast data transmission from an evolved Node B (eNB); means for sending a negative acknowledgement (NACK) upon unsuccessfully decoding the received multicast/broadcast data transmission; and means for receiving a retransmission of the multicast/broadcast data transmission based on network coding automatic repeat request (NC-ARQ).
 61. The apparatus of claim 44, further comprising means for receiving a configuration to receive the multicast/broadcast data transmission through rank 1 transmissions from an evolved Node B (eNB).
 62. The apparatus of claim 61, further comprising: means for determining channel quality indictor (CQI) feedback based on one of a space-frequency block code (SFBC) diversity scheme, or an SFBC and a frequency switched transmit diversity (FSTD) diversity scheme; and means for sending the CQI to the eNB.
 63. The apparatus of claim 44, further comprising: means for receiving a configuration to receive the multicast/broadcast data transmission through multi-user multiple input multiple output (MU-MIMO) from an evolved Node B (eNB); means for determining channel quality indicator (CQI) feedback and a precoding matrix indicator (PMI); and means for sending the determined CQI and PMI to the eNB.
 64. An apparatus for providing a multicast/broadcast data transmission via a group bearer, the apparatus being an evolved Node B (eNB), comprising: means for determining a type of the group bearer; and means for sending a paging message comprising the type of the group bearer to a set of user equipments (UEs).
 65. The apparatus of claim 64, wherein the type of the group bearer is determined to be one of idle, hybrid, or connected.
 66. The apparatus of claim 64, further comprising means for determining at least one of a type of the multicast/broadcast data transmission, an importance of the multicast/broadcast data transmission, or a number of UEs in the set of UEs, wherein the type of the group bearer is determined based on the determined at least one of the type of the multicast/broadcast data transmission, the importance of the multicast/broadcast data transmission, or the number of UEs in the set of UEs.
 67. The apparatus of claim 64, wherein the paging message further comprises a group identifier associated with the set of UEs, and the apparatus further comprises means for sending group bearer parameters to the set of UEs.
 68. The apparatus of claim 67, wherein the paging message further comprises a group radio network temporary identifier (G-RNTI), and the apparatus further comprises means for scrambling the group bearer parameters based on the G-RNTI.
 69. The apparatus of claim 67, wherein the group bearer parameters comprise at least one of a bearer identifier, the group identifier, the G-RNTI, a list of UEs in the set of UEs, a radio link control (RLC)/packet data convergence protocol (PDCP) configuration, a quality of service (QoS) profile, an Internet Protocol (IP) address, and the type of the group bearer.
 70. The apparatus of claim 67, wherein the group bearer parameters comprise a group discontinuous reception (DRX) configuration, and the apparatus further comprises means for transmitting the multicast/broadcast data transmission to the set of UEs based on the group DRX configuration when the group bearer is activated.
 71. The apparatus of claim 64, further comprising: means for sending a multicast/broadcast data transmission packet to the set of UEs through the group bearer; and means for receiving a negative acknowledgement (ACK) (NACK) from each UE in the set of UEs that is unable to decode the multicast/broadcast data transmission packet, wherein ACKs are not received from UEs in the set of UEs that are able to decode the multicast/broadcast data transmission packet.
 72. The apparatus of claim 71, wherein each NACK is received in a PUCCH format 1 message.
 73. The apparatus of claim 71, wherein each NACK is received in a same resource shared by each UE in the set of UEs, wherein the resource is associated with a physical downlink control channel (PDCCH) used for scheduling the multicast/broadcast data transmission.
 74. The apparatus of claim 64, wherein the type of the group bearer is determined to be hybrid or connected, and the apparatus further comprises means for receiving channel quality indicator (CQI) feedback from UEs in the set of UEs that are in a radio resource control (RRC) connected mode.
 75. The apparatus of claim 74, further comprising: means for determining a modulation and coding scheme (MCS) based on the received CQI; and means for transmitting the multicast/broadcast data transmission based on the determined MCS.
 76. The apparatus of claim 75, wherein the MCS is determined based on a lowest received CQI.
 77. The apparatus of claim 74, further comprising: means for determining a channel quality indicator (CQI) feedback configuration for each UE in the set of UEs based on at least one of CQI feedback or measurement reports received from the UE; means for sending the determined CQI feedback configuration to each UE; and means for receiving CQI feedback from each UE in the set of UEs based on the provided CQI feedback configuration.
 78. The apparatus of claim 74, further comprising: means for sending a multicast/broadcast data transmission packet; and means for configuring UEs in the set of UEs to send the CQI feedback when unable to decode the multicast/broadcast data transmission packet and to refrain from sending the CQI feedback when able to decode the multicast/broadcast data transmission packet.
 79. The apparatus of claim 74, further comprising: means for sending a CQI threshold to UEs in the set of UEs; means for sending a multicast/broadcast data transmission packet; and means for configuring UEs in the set of UEs to send the CQI feedback when CQI is less than the CQI threshold and to refrain from sending the CQI feedback when CQI is greater than the CQI threshold.
 80. The apparatus of claim 74, further comprising means for checking for a NACK on a CQI resource and an ACK/NACK resource, wherein the ACK/NACK resource is associated with a physical downlink control channel (PDCCH) used for scheduling the multicast/broadcast data transmission.
 81. The apparatus of claim 64, further comprising: means for sending the multicast/broadcast data transmission; means for receiving a negative acknowledgement (NACK) with respect to the multicast/broadcast data transmission; and means for retransmitting the multicast/broadcast data transmission based on network coding automatic repeat request (NC-ARQ).
 82. The apparatus of claim 64, further comprising means for sending the multicast/broadcast data transmission through a rank 1 transmission.
 83. The apparatus of claim 81, wherein the multicast/broadcast data transmission is sent by utilizing one of a space-frequency block code (SFBC) diversity scheme, or an SFBC and a frequency switched transmit diversity (FSTD) diversity scheme.
 84. The apparatus of claim 64, further comprising means for sending the multicast/broadcast data transmission to the set of UEs through multi-user multiple input multiple output (MU-MIMO).
 85. An apparatus for push to talk (PTT)/push to everything (PTX) communication, comprising: means for receiving a PTT/PTX message for a set of user equipments (UEs); means for establishing one of a unicast bearer, a group bearer, or a Multimedia Broadcast Multicast Service (MBMS) bearer based on at least one of the PTT/PTX message or the set of UEs; and means for sending the PTT/PTX message through the established bearer to the set of UEs.
 86. The apparatus of claim 85, further comprising means for determining whether to establish the unicast bearer, the group bearer, or the MBMS bearer based on at least one of bearer capabilities of UEs in the set of UEs, a number of UEs in the set of UEs, whether file repair is needed for the PTT/PTX communication, a type of the PTT/PTX communication, or an importance of the PTT/PTX communication.
 87. An apparatus for receiving a multicast/broadcast data transmission via a group bearer, the apparatus being a user equipment (UE), comprising: a processing system configured to: receive a paging message comprising a type of the group bearer; and determine whether to remain in or change to a radio resource control (RRC) idle mode or an RRC connected mode based on the type of the group bearer received in the paging message.
 88. An apparatus for providing a multicast/broadcast data transmission via a group bearer, the apparatus being an evolved Node B (eNB), comprising: a processing system configured to: determine a type of the group bearer; and send a paging message comprising the type of the group bearer to a set of user equipments (UEs).
 89. An apparatus for push to talk (PTT)/push to everything (PTX) communication, comprising: a processing system configured to: receive a PTT/PTX message for a set of user equipments (UEs); establish one of a unicast bearer, a group bearer, or a Multimedia Broadcast Multicast Service (MBMS) bearer based on at least one of the PTT/PTX message or the set of UEs; and send the PTT/PTX message through the established bearer to the set of UEs.
 90. A computer program product for receiving a multicast/broadcast data transmission via a group bearer in a user equipment (UE), comprising: a computer-readable medium comprising code for: receiving a paging message comprising a type of the group bearer; and determining whether to remain in or change to a radio resource control (RRC) idle mode or an RRC connected mode based on the type of the group bearer received in the paging message.
 91. A computer program product for providing a multicast/broadcast data transmission via a group bearer in an evolved Node B (eNB), comprising: a computer-readable medium comprising code for: determining a type of the group bearer; and sending a paging message comprising the type of the group bearer to a set of user equipments (UEs).
 92. A computer program product for push to talk (PTT)/push to everything (PTX) communication, comprising: a computer-readable medium comprising code for: receiving a PTT/PTX message for a set of user equipments (UEs); establishing one of a unicast bearer, a group bearer, or a Multimedia Broadcast Multicast Service (MBMS) bearer based on at least one of the PTT/PTX message or the set of UEs; and sending the PTT/PTX message through the established bearer to the set of UEs. 